-
Notifications
You must be signed in to change notification settings - Fork 170
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
Update the group of Service in the examples and tests #156
Conversation
The group of Service can be either empty ("") or "v1", but not "core", so as other resources (ConfigMap, Pod, Secret, PersistentVolumeClaim and etc.).
/assign @barney-s |
@@ -13,7 +13,7 @@ spec: | |||
matchLabels: | |||
app.kubernetes.io/name: "wordpress-01" | |||
componentKinds: | |||
- group: core | |||
- group: v1 |
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 understand this change. Why change "" to v1 in the others ?
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.
per Janet's comment: #112 (comment).
It seems v1
makes more sense than ""
.
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: barney-s, nan-yu 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 |
The group of Service can be either "v1" or empty (""), but not "core",
so as other resources (ConfigMap, Pod, Secret, PersistentVolumeClaim and
etc.).