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

OCPBUGS-31384: use RotatedSigningCASecret controller in update only mode #1659

Merged
merged 3 commits into from Apr 4, 2024

Conversation

tkashem
Copy link
Contributor

@tkashem tkashem commented Apr 2, 2024

UseSecretUpdateOnly is intended as a short term hack for a very specific use case,
and it works in tandem with a particular carry patch applied to the openshift kube-apiserver.
(openshift/kubernetes#1924)

we will remove this when we migrate all of the affected secret
objects to their intended type: https://issues.redhat.com/browse/API-1800

in short tls secrets used by this operator are reconciled by multiple controllers at the same time without any coordination. the issue is that the secret's crypto material can be regenerated, which has serious consequences for the platform as it can break external clients and the cluster itself.

xref: openshift/library-go#1705
xref: openshift/kubernetes#1924

@tkashem
Copy link
Contributor Author

tkashem commented Apr 2, 2024

/cc @p0lyn0mial

@openshift-ci openshift-ci bot requested a review from p0lyn0mial April 2, 2024 18:29
@tkashem
Copy link
Contributor Author

tkashem commented Apr 2, 2024

/hold

(until openshift/kubernetes#1924 merges)

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Apr 2, 2024
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 2, 2024

// we will remove this when we migrate all of the affected secret
// objects to their intended type: https://issues.redhat.com/browse/API-1800
UseSecretUpdateOnly: true,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we should also apply it to the RotatedSelfSignedCertKeySecret controller, right ?

we will remove this when we migrate all of the affected secret
objects to their intended type
see: https://issues.redhat.com/browse/API-1800
@tkashem tkashem changed the title use RotatedSigningCASecret controller in update only mode OCPBUGS-31384: use RotatedSigningCASecret controller in update only mode Apr 2, 2024
@openshift-ci-robot openshift-ci-robot added jira/severity-critical Referenced Jira bug's severity is critical for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. labels Apr 2, 2024
@openshift-ci-robot
Copy link

@tkashem: This pull request references Jira Issue OCPBUGS-31384, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.16.0) matches configured target version for branch (4.16.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @wangke19

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

UseSecretUpdateOnly is intended as a short term hack for a very specific use case,
and it works in tandem with a particular carry patch applied to the openshift kube-apiserver.
(openshift/kubernetes#1924)

we will remove this when we migrate all of the affected secret
objects to their intended type: https://issues.redhat.com/browse/API-1800

in short tls secrets used by this operator are reconciled by multiple controllers at the same time without any coordination. the issue is that the secret's crypto material can be regenerated, which has serious consequences for the platform as it can break external clients and the cluster itself.

xref: openshift/library-go#1705
xref: openshift/kubernetes#1924

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci-robot openshift-ci-robot added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Apr 2, 2024
@openshift-ci openshift-ci bot requested a review from wangke19 April 2, 2024 23:52
@tkashem
Copy link
Contributor Author

tkashem commented Apr 2, 2024

/retest-required

@p0lyn0mial
Copy link
Contributor

it also requires openshift/kubernetes#1929

@p0lyn0mial
Copy link
Contributor

/retest-required

@p0lyn0mial
Copy link
Contributor

/lgtm

@p0lyn0mial
Copy link
Contributor

/cc @vrutkovs

@p0lyn0mial
Copy link
Contributor

/retest-required

1 similar comment
@tkashem
Copy link
Contributor Author

tkashem commented Apr 3, 2024

/retest-required

@tkashem
Copy link
Contributor Author

tkashem commented Apr 3, 2024

/retest

@tkashem
Copy link
Contributor Author

tkashem commented Apr 3, 2024

/retest-required

@tkashem
Copy link
Contributor Author

tkashem commented Apr 3, 2024

/retest-required

1 similar comment
@tkashem
Copy link
Contributor Author

tkashem commented Apr 4, 2024

/retest-required

@p0lyn0mial
Copy link
Contributor

e2e-gcp-operator fails on TestCertRotationStompOnBadType for which i've opened openshift/kubernetes#1932

in general due to the platform's long history (spanning several years)
and the complexity of ensuring that resources were consistently created with only one type
I think that we should relax the restrictions on allowed type mutation transitions.

@p0lyn0mial
Copy link
Contributor

issues like event happened 4009 times, something is wrong: node/ip-10-0-102-140.us-east-2.compute.internal hmsg/e82226461c - reason/ConfigMapUpdated Updated ConfigMap/kube-control-plane-signer-ca -n openshift-kube-apiserver-operator: result=reject will be fixed by #1661

@p0lyn0mial
Copy link
Contributor

p0lyn0mial commented Apr 4, 2024

/retest-required

#1661 merged which should unblock all jobs except e2e-gcp-operator which will be unblocked by openshift/kubernetes#1932

@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Apr 4, 2024
@p0lyn0mial
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Apr 4, 2024
Copy link
Contributor

openshift-ci bot commented Apr 4, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: p0lyn0mial, tkashem

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

@tkashem
Copy link
Contributor Author

tkashem commented Apr 4, 2024

/hold cancel

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Apr 4, 2024
Copy link
Contributor

openshift-ci bot commented Apr 4, 2024

@tkashem: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/e2e-aws-operator-disruptive-single-node 6c448ef link false /test e2e-aws-operator-disruptive-single-node
ci/prow/k8s-e2e-gcp-serial 6c448ef link false /test k8s-e2e-gcp-serial
ci/prow/e2e-gcp-operator-single-node 6c448ef link false /test e2e-gcp-operator-single-node

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-bot openshift-merge-bot bot merged commit 7599746 into openshift:master Apr 4, 2024
12 of 15 checks passed
@openshift-ci-robot
Copy link

@tkashem: Jira Issue OCPBUGS-31384: Some pull requests linked via external trackers have merged:

The following pull requests linked via external trackers have not merged:

These pull request must merge or be unlinked from the Jira bug in order for it to move to the next state. Once unlinked, request a bug refresh with /jira refresh.

Jira Issue OCPBUGS-31384 has not been moved to the MODIFIED state.

In response to this:

UseSecretUpdateOnly is intended as a short term hack for a very specific use case,
and it works in tandem with a particular carry patch applied to the openshift kube-apiserver.
(openshift/kubernetes#1924)

we will remove this when we migrate all of the affected secret
objects to their intended type: https://issues.redhat.com/browse/API-1800

in short tls secrets used by this operator are reconciled by multiple controllers at the same time without any coordination. the issue is that the secret's crypto material can be regenerated, which has serious consequences for the platform as it can break external clients and the cluster itself.

xref: openshift/library-go#1705
xref: openshift/kubernetes#1924

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

This PR has been included in build ose-cluster-kube-apiserver-operator-container-v4.16.0-202404041616.p0.g7599746.assembly.stream.el9 for distgit ose-cluster-kube-apiserver-operator.
All builds following this will include this PR.

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. jira/severity-critical Referenced Jira bug's severity is critical for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants