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
peer-pods: validate CM and Secret are set #353
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.
LGTM. Thanks @snir911 !
1e6b3c4
to
b1b4bb3
Compare
4b751a4
to
b209fd4
Compare
Premerge testing successful. |
Hi @snir911 ! I had approved your original submission as the change was simple to understand, despite the lack of change log. I must admit that now things are a lot harder... Not sure if I'll be able to approve this PR today if I need to guess everything by myself. |
We usually fetching cloud-provider name from either the peer-pods CM CLOUD_PROVIDER value or from the infra object, as cloud provider is not expected to be changed at runtime this commit moves its fetching into the image-generator initialization. Additionally fetching the cloud-provider solely from the infra Object to avoid relying on user input (from peer-pods CM) Signed-off-by: Snir Sheriber <ssheribe@redhat.com>
in peer-pods ConfigMap or Secret it's assumed essential values will not be modified once set and kataConfig was created Signed-off-by: Snir Sheriber <ssheribe@redhat.com>
Signed-off-by: Snir Sheriber <ssheribe@redhat.com>
b209fd4
to
7de0bf7
Compare
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.
Thanks for the work and patience @snir911 !
No description provided.