Skip to content

add namespace to deduplication tuple #41

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

Merged
merged 1 commit into from
Jul 12, 2018

Conversation

novas0x2a
Copy link
Contributor

@novas0x2a novas0x2a commented Apr 13, 2018

helm charts can deploy to multiple namespaces at once, so compare on
(namespace, name, kind, version) instead of just (name, kind, version).

(We're deploying ResourceQuotas with the same name across multiple namespaces)

@databus23
Copy link
Owner

databus23 commented Apr 16, 2018

Did you test this? In my case the Namespace is empty. I guess thats because it was not specified in the templates rendered by helm. Maybe we should provide a string like RELEASE_NAMESPACE for namespace if its empty.

@databus23
Copy link
Owner

Or maybe we even pass in the release namespace into the Parse method to fill it in if its not specified in the spec.

@novas0x2a
Copy link
Contributor Author

Okay, finally got around to learning more about the helm api; this seems to do the right thing now.

@novas0x2a
Copy link
Contributor Author

Noticed there was a conflict; rebased it.

@mumoshu
Copy link
Collaborator

mumoshu commented Jun 27, 2018

@novas0x2a Sorry but this got to conflict badly with the current master. Would you mind rebasing when you have some time? I'm still considering this as an important edge-case to be addressed.

helm charts can deploy to multiple namespaces at once, so compare on
(namespace, name, kind, version) instead of just (name, kind, version).

If no namespace is parsed from the manifest, the helm release namespace
is used instead.
@novas0x2a
Copy link
Contributor Author

rebased again.

@novas0x2a
Copy link
Contributor Author

@mumoshu @databus23?

@mumoshu
Copy link
Collaborator

mumoshu commented Jul 12, 2018

@novas0x2a Sorry it took some time to test this manually on my side. LGTM. Thanks for your patience, and awesome work!

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.

3 participants