-
Notifications
You must be signed in to change notification settings - Fork 774
Remove ubi suffix for 9.x images #8509
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
Conversation
barkbay
left a comment
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.
Change technically LGTM but should we document that it is intended that the suffix will no longer be set for 9.x?
Either here:
--- a/cmd/manager/main.go
+++ b/cmd/manager/main.go
@@ -322,7 +322,7 @@ func Command() *cobra.Command {
cmd.Flags().Bool(
operator.UBIOnlyFlag,
false,
- fmt.Sprintf("Use only UBI container images to deploy Elastic Stack applications. UBI images are only available from 7.10.0 onward. Cannot be combined with %s", operator.ContainerSuffixFlag),
+ fmt.Sprintf("Use only UBI container images to deploy Elastic Stack applications. UBI images are only available from 7.10.0 onward. Ignored from 9.x as default images are based on UBI. Cannot be combined with %s", operator.ContainerSuffixFlag),
)
cmd.Flags().Bool(
operator.ValidateStorageClassFlag,Or in the documentation?
+1 to that. I think if you add it as suggested by Michael and here https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s-operator-config.html we should be good. |
I updated both the places. Thank you! |
barkbay
left a comment
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
31f8a89 to
e78981d
Compare
With 9.x release all images should be based off of ubi, so we should no longer need the -ubi suffix