-
-
Notifications
You must be signed in to change notification settings - Fork 6
feat: Add v1alpha2 for SecretClass, rename experimentalGenerateSamAccountName #634
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
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is mostly done, but I left a few small comments/reminders.
mkdir -p extra | ||
cargo run --bin stackable-"${OPERATOR_NAME}" -- crd > extra/crds.yaml |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This eventually needs to be upstreamed into operator-templating
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added a comment in the PR description about this
k8s_yaml(helm( | ||
'deploy/helm/' + operator_name, | ||
name=operator_name, | ||
namespace="stackable-operators", | ||
set=[ | ||
'image.repository=' + registry + '/' + operator_name, | ||
'telemetry.consoleLog.level=trace,h2=off', | ||
], | ||
)) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also needs to be upstreamed into operator-templating
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added a comment in the PR description about this
761a56c
to
29ccbdf
Compare
I can not approve my own PR but LGTM |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@razvan reported
❯ helm upgrade --install --namespace stackable-operators secret-operator deploy/helm/secret-operator/
Error: unable to build kubernetes objects from release manifest: resource mapping not found for name: "tls" namespace: "" from "": no matches for kind "SecretClass" in version "secrets.stackable.tech/v1alpha1"
ensure CRDs are installed first
I guess the easiest solution is to move the SecretClass creation into a Job, WDYT?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can we have an initial crd deployment done by Helm/OLM as before?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would vote "no". There should be no need for it, as the operator immediately deploys it when starting up for the first time.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This moved into a decision: https://github.com/stackabletech/decisions/issues/62.
I'll put this here for lack of a better place now. I tried installing this op version with OLM on OpenShift. OLM of course has the same problem as Helm (see comment above). It tries to create a I manually added the exported CRDs to OLM, but then the operator refuses to start with this error:
No idea if this is expected or a bug. My 2 cents: I don't know why you decided to take CRD management out of the hands of package managers because I don't remember discussing it and I find no explanation. But I think one implication of this is that we now have to implement Helm ourselves by having to ensure object creation order at least. |
Tests on OKD are 🟢 though no test was added or updated for this PR. I removed Then I ran the test suite:
|
Part of stackabletech/issues#642
Note
Load-balancing over the secret-op DaemonSet Pods seems to work fine, but we should also test it on a cloud provider with multiple nodes as well.
This PR marks
samAccountName
as non-experimental as per #627. It is the first use of thestackable-versioned
macro as well as the conversion webhook machinery.Note
This PR makes changes to things that are templated by operator-templating! We are aware of this and will have a diff until we roll this out to all operators and update operator-templating. secret-operator is our guinea-pig