Skip to content

Rebase to v2.4.1 from upstream #5

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

Merged
merged 35 commits into from
Apr 5, 2022

Conversation

arjunrn
Copy link

@arjunrn arjunrn commented Apr 4, 2022

No description provided.

stevehipwell and others added 30 commits February 2, 2022 10:48
* Merge tags on service and ingress

* update doc
…2478)

* Adding support of ingressClassParams in helm charts

* Update charts to let users to create ingressClassParams with specs

* Simplying the spec in values yaml

* Adding support for customer's ingressClassParams

* Using values fields directly instead of function

* eks1.19 doesn't allow null spec and need move if check out from spec block.
* add support for loadBalancerClass

* throw error in case of unallocated NodePort

* centralize IsServiceSupported logic

* handle lb type annotation change for type LoadBalancer

* refactor IsServiceSupported
* fix typo in annotations doc

* make keepTLSSecret true by default

Update README
  - Update prerequisites
  - Provide instructions to remove iamserviceaccount
* doc updates for v2.4.0

* update external dns example
added region and vpc_id arguments for installing the controller
…er-name

Make e2e LB name test work with clusters that have . in the name
Correct documentation typo error
…icates

remove undesired certificates before adding new ones
Upgrade webhook server minimum version to TLS1.3
* monitor secret resources ony if necessary

* removes the default watch for all secret resources in the cluster
* create watch for specific secret resource if required for OIDC feature
* do not configure rbac permissions for secrets by default
* provide helm chart configuration options for specific secret resources

* remove option to configure specific secret names

* use channel for secrets event
…-sigs#2524)

* mark pod with readiness gate as healthy when deleting TGB

* list pod keys

Co-authored-by: Kishor Joshi <[email protected]>
* cut v2.4.1 release

* Helm chart for v2.4.1 release
@openshift-ci openshift-ci bot requested review from alebedev87 and Miciah April 4, 2022 16:54
@openshift-ci
Copy link

openshift-ci bot commented Apr 4, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: arjunrn

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 Apr 4, 2022
@openshift-ci
Copy link

openshift-ci bot commented Apr 4, 2022

@arjunrn: 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.

@alebedev87
Copy link

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Apr 5, 2022
@arjunrn
Copy link
Author

arjunrn commented Apr 5, 2022

/label docs-approved
/label qe-approved
/label px-approved

@openshift-ci openshift-ci bot added docs-approved Signifies that Docs has signed off on this PR qe-approved Signifies that QE has signed off on this PR px-approved Signifies that Product Support has signed off on this PR labels Apr 5, 2022
@openshift-merge-robot openshift-merge-robot merged commit bdf62d2 into openshift:main Apr 5, 2022
@arjunrn arjunrn deleted the rebase-2.4.1 branch April 5, 2022 09:35
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. docs-approved Signifies that Docs has signed off on this PR lgtm Indicates that a PR is ready to be merged. px-approved Signifies that Product Support has signed off on this PR qe-approved Signifies that QE has signed off on this PR
Projects
None yet
Development

Successfully merging this pull request may close these issues.