Skip to content
This repository has been archived by the owner on Nov 8, 2019. It is now read-only.

Env variable to disable/enable namespace isolation policy #24

Merged

Conversation

luke-mino-altherr
Copy link
Contributor

No description provided.

@@ -35,6 +35,9 @@
KUBE_API_ROOT = os.environ.get('KUBE_API_ROOT',
'http://kubernetes-master:8080/api/v1/')

# Allow the user to enable/disable namespace isolation policy
NAMESPACE_ISOLATION = os.environ.get('NAMESPACE_ISOLATION', 'true')
Copy link
Member

Choose a reason for hiding this comment

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

I think calling this NAMESPACE_ISOLATION is a bit confusing, since namespace isolation will still be in effect if policy is declared, just not when no policy is declared.

A more apt name might be something like "DEFAULT_POLICY", with options for "ns_isolation", "allow". This means we could potentially support multiple other default behaviors in the future.

@@ -35,6 +35,9 @@
KUBE_API_ROOT = os.environ.get('KUBE_API_ROOT',
'http://kubernetes-master:8080/api/v1/')

# Allow the user to enable/disable namespace isolation policy
DEFAULT_POLICY = os.environ.get('DEFAULT_POLICY', 'ns_isolation')
Copy link
Member

Choose a reason for hiding this comment

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

I think the default behavior should be no ns_isolation.

@caseydavenport
Copy link
Member

LGTM. You'll want to update the calico-docker docs to reflect this as well.

https://github.com/projectcalico/calico-docker/blob/master/docs/kubernetes/KubernetesIntegration.md

luke-mino-altherr added a commit that referenced this pull request Aug 26, 2015
Env variable to disable/enable namespace isolation policy
@luke-mino-altherr luke-mino-altherr merged commit fafb644 into projectcalico:master Aug 26, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants