This repository has been archived by the owner on Oct 13, 2021. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added ClusterGitTrack #145
Added ClusterGitTrack #145
Changes from all commits
a5ccd08
3587162
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Since we know this can destroy clusters, I'm very tempted to not maintain this backwards compatibility.
We are on an alpha version and I think, given the severity of this change, we will skip the
0.4.0
release and go straight to0.5.0
. People will expect breaking changes and I think there are better ways to handle this.I discussed with @mthssdrbrg yesterday about having the
GitTrackObject
controller look for OwnerReferences pointing to the wrong namespace and "orphaning" the GitTracks. This could then be exposed as a metric which we can note in the release people should look for and make sure it goes to zero, what do you think to that approach instead? Easy migration vs backwards compatiblityThere 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 agree, it would be better to break the current behavior in this case.
I like the idea of exposing the metric and breaking the owner reference.