Skip to content
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

disable manageStatus #34

Merged
merged 1 commit into from Aug 13, 2019
Merged

Conversation

jmontleon
Copy link
Collaborator

No description provided.

@jmontleon
Copy link
Collaborator Author

controller and ui will probably need api versions adjusted. Old settings seem forward compatible, so shouldn't be a problem to update them. This should get velero/restic working at least, back to 3.7.

@jmontleon
Copy link
Collaborator Author

Special thanks to @fabianvf for saving our bacon.

@djwhatle
Copy link
Contributor

Will test this on a 4.x cluster, then add approval if it works ⚡

@djwhatle
Copy link
Contributor

Works on 4.1

@jmontleon
Copy link
Collaborator Author

The scc clusterrole isn't working on 3.7. Let me see what I can find.

@jmontleon jmontleon force-pushed the disable-status branch 3 times, most recently from 3348b40 to 0307b43 Compare August 12, 2019 18:56
@@ -186,18 +186,47 @@ roleRef:
name: cluster-admin
apiGroup: rbac.authorization.k8s.io
---
kind: ClusterRoleBinding
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not the preferred way anymore, but the new way doesn't seem to work with 3.7. This is fine... it's just creating a new scc instead of a clusterrole for the existing one.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For 4.x we can keep the clusterrole(binding) via OLM.

Copy link
Contributor

@djwhatle djwhatle left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Worked for me on 4.1. I'm not able to remove mig components anymore by modifying the MigrationController resource, but I think being able to deploy to 3.7-3.10 is much more important than the loss of that functionality, we can always figure out why that's not working if it's important down the road.

@@ -33,7 +33,7 @@ spec:
served: true
storage: true
---
apiVersion: rbac.authorization.k8s.io/v1
apiVersion: rbac.authorization.k8s.io/v1beta1
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How does the apiVersion change to beta1 contribute to the solution? Just curious?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

RBAC went to v1 in 1.8, so for 3.7 clusters they would only have the 'v1beta1' endpoint.

Assuming that the v1beta1 endpoint is still present on newer versions so by using that endpoint could be way to have same code work with rbac on 3.7+

@@ -3,3 +3,4 @@
group: migration.openshift.io
kind: MigrationController
role: /opt/ansible/roles/migrationcontroller
manageStatus: False
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍 That's easy.

Copy link
Contributor

@jortel jortel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants