operator-sdk
operator-sdk copied to clipboard
Helm Operator Tutorial
In https://github.com/open-policy-agent/gatekeeper/tree/master/charts/gatekeeper
-IMG ?= controller:latest
+IMG ?= $(IMAGE_TAG_BASE):$(VERSION)
I may be misunderstanding but shouldn't it be v$(VERSION)
? As-is it will tag it as 0.0.1
Yes. It could be, since its a tag. @thomasmckay would you mind submitting a PR to fix the Makefile scaffolding to have v
in the version, or add the v
prefix to the IMG
tag. https://github.com/operator-framework/operator-sdk/blob/280335593c76c1fb14ce96100938f140ddb42659/testdata/helm/memcached-operator/Makefile#L6
Thanks for brining it up!
Hi @varshaprasad96 , I would like to know the use of "overrideValues" in watches.yaml. If the values can be overridden by adding in CR spec, then what is the use of adding overrideValues field again in watches.yaml? Could you please share your thoughts on this? It would be really grateful if you can explain me with an example.
Thanks !
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen
.
If this issue is safe to close now please do so with /close
.
/lifecycle stale
Hello everyone, I've been following this project recently and would like to contribute. What is the problem with this good first issue? Can you describe it in detail? I want to spend some time trying to solve it.
Stale issues rot after 30d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle rotten
.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen
.
If this issue is safe to close now please do so with /close
.
/lifecycle rotten /remove-lifecycle stale
Rotten issues close after 30d of inactivity.
Reopen the issue by commenting /reopen
.
Mark the issue as fresh by commenting /remove-lifecycle rotten
.
Exclude this issue from closing again by commenting /lifecycle frozen
.
/close
@openshift-bot: Closing this issue.
In response to this:
Rotten issues close after 30d of inactivity.
Reopen the issue by commenting
/reopen
. Mark the issue as fresh by commenting/remove-lifecycle rotten
. Exclude this issue from closing again by commenting/lifecycle frozen
./close
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.