Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release 4.12 rebase latest #2047

Merged

Conversation

enxebre
Copy link
Member

@enxebre enxebre commented Jan 17, 2023

What this PR does / why we need it:

git fetch origin
git co -b release-4.12-rebase origin/release-4.12
git rebase origin/main
solve conflict in control-plane-operator/controllers/hostedcontrolplane/cno/clusternetworkoperator.go
git push enxebre release-4.12-rebase

Which issue(s) this PR fixes (optional, use fixes #<issue_number>(, fixes #<issue_number>, ...) format, where issue_number might be a GitHub issue, or a Jira story:
Fixes #

Checklist

  • Subject and description added to both, commit and PR.
  • Relevant issues have been referenced.
  • This change includes docs.
  • This change includes unit tests.

csrwng and others added 30 commits December 13, 2022 00:43
If the hcco is not available, the cpo will wait indefinitely for it to
update hcp conditions to indicate that guest resources have been
deleted. To solve that, the hcco will periodically update a condition to
let the CPO that it's working on deletion. If the condition is not
updated after a certain amount of time, the CPO gives up waiting and
proceeds with the rest of the deletion.
fix(ho): Use v1alpha1 ownerRef for future CPO managed components
test: e2e: remove node checks during NodePool upgrade test
Revert "add KAS egress network policy"
HypershiftAWSLoadBalancerCrossZoneLoadBalancingEnabled applies https://kubernetes-sigs.github.io/aws-load-balancer-controller/v2.1/guide/service/annotations/
service.beta.kubernetes.io/aws-load-balancer-cross-zone-load-balancing-enabled in the load balancer services of the hosted control plane endpoints.
AWS Private link requires endpoint and service endpoints to exist in the same underlying zone. To ensure that requirement is satisfied in Regions with more than 3 zones, managed services create subnets in all of them. That and having this enabled in the load balancers would make the private link communication to always succeed.
Prevent cluster deletion hangs by using heartbeat condition
This improve UX by removing the need to pre create a kube secret and require only a string as input instead. This align UX with RolesRef field
…terval

external-dns: set AWS batch internal to 10s
Signed-off-by: David Vossel <davidvossel@gmail.com>
add missing app label to HCP components
fix(ho): Set restart date annotation back
…ss-v2

Add default kubevirt guest cluster storageclass
Add support for additional allowed principals for AWS hosted cluster VPC Endpoint Services
fix(cpo): Remove storage from mgmt cluster for IBM Cloud
adjust rate interval on hypershift:controlplane:component_cpu_usage_s…
This extend existing metrics exposed by the HO to include Expose proxy, identityProviders and limited support metrics. These metrics are useful to infer symptons and point to causes when observing a fleet of clusters. E.g. Lets say we notice a subset of customers having IDP issues but no reported outages on github. We would be able to analyze the metrics and indeed say that github was having issues if we had outages fleetwide across github.
These metrics are used in ROSA today. In future if they grow in a very opinionated way we might want to decouple them from the HO.
The label is dropped when reported in metrics if it doesn't have a
value.
Updated secret permissions to 0640
This introduces inital support for label/tait propagation from NodePools to Nodes honouring the following functional reqs:
- Propagate only once on Node creation. In future we might enable further automated or controller reconciliation.
- Enable consumers to choose the labels/taints to be synced.
Expose proxy, identityProviders and limited support metrics
Add value to hosted control plane namespace label
Add support to propagate labels from NodePools to Nodes
…concile

fix cluster csi driver reconcile
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 17, 2023

@enxebre: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.

In response to this:

Release 4.12 rebase latest

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 17, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: enxebre

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 17, 2023
@csrwng
Copy link
Contributor

csrwng commented Jan 17, 2023

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jan 17, 2023
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 8b982f3 and 2 for PR HEAD 80e0e90 in total

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 17, 2023

@enxebre: all tests passed!

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@openshift-merge-robot openshift-merge-robot merged commit 8f9c6a2 into openshift:release-4.12 Jan 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.