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
Use Apps api over extensions #2611
Conversation
failed with the following error
|
@@ -215,7 +215,7 @@ rules: | |||
- update | |||
- delete | |||
- apiGroups: | |||
- extensions | |||
- apps |
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.
For the upgrade test, we'll need to revert any changes to this file
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 have a change coming in #2522 (hopefully merged today) that will update the rbac needed for the upgrade test. We'll need to do something similar here. This helps us catch what needs to be upgraded by users for the next release.
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.
done
Spec: apps.DaemonSetSpec{ | ||
Selector: &metav1.LabelSelector{ | ||
MatchLabels: map[string]string{ | ||
"app": discoverDaemonsetName, |
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.
why do we need the selector for the daemonset now?
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.
selector is required to match labels in apps resources
https://github.com/kubernetes/kubernetes/blob/master/pkg/apis/apps/validation/validation.go
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.
we still need to update selectors in deployments so CI can pass
Like Travis said, I'd like to see what the upgrade procedure is to go from 0.9.x to master with these changes, but other than that I think it looks good. |
@rootfs Why are we going to use |
cc @yanniszark for cassandra changes @dyusupov for edgefs changes |
I don't have a problem supporting v1 api |
fa2aae2
to
7cbd6b1
Compare
looks there was a test flake on aws 1.12, other instances went well |
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.
@@ -403,7 +403,7 @@ subjects: | |||
name: rook-ceph-system | |||
namespace: ` + namespace + ` | |||
--- | |||
apiVersion: apps/v1beta1 | |||
apiVersion: extensions/v1beta1 |
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.
please revert this change to ceph_manifests_v0.9.go
0545a07
to
582b493
Compare
@@ -1403,10 +1403,8 @@ | |||
"github.com/yanniszark/go-nodetool/nodetool", | |||
"k8s.io/api/apps/v1", | |||
"k8s.io/api/apps/v1beta1", |
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'm wondering why this dependency is still here after switching to apps/v1.
Any idea why it is still a dependency? Is it used by "old" or somewhere in test code?
Checking the PR head for files containing "/extensions/v1beta" returned only files from the vendor folder, so everything seems to have been updated.
@galexrt as for why vendor still contains |
@@ -41,7 +41,7 @@ rules: | |||
- update | |||
- delete | |||
- apiGroups: | |||
- extensions | |||
- apps |
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 is only used for upgrades from 0.8 to 0.9, so we'll need to revert this. We'll need something similar for the v0.9 to v1.0 upgrade before we release though
@@ -204,7 +204,7 @@ rules: | |||
- update | |||
- delete | |||
- apiGroups: | |||
- extensions | |||
- apps |
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.
if there are changes to the rbac i would have expected the upgrade_test.go to need an update, otherwise the rbac will not be updated in the test. See here for an example of updating the rbac for a similar change. The upgrade test is what helps us put the final upgrade documentation ready when it's time for release.
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
@@ -155,6 +155,9 @@ func (s *UpgradeSuite) updateClusterRoles() error { | |||
if _, err := s.k8sh.DeleteResource("ClusterRole", "rook-ceph-global"); err != nil { | |||
return err | |||
} | |||
if _, err := s.k8sh.DeleteResource("ClusterRole", "rook-ceph-cluster-mgmt"); err != nil { |
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.
Do we also need to add the rook-ceph-system role? Looks like there is a change there as well.
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
Signed-off-by: Huamin Chen <hchen@redhat.com>
Description of your changes:
fix #2601
Which issue is resolved by this Pull Request:
Resolves #
Checklist:
make codegen
) has been run to update object specifications, if necessary.