You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 21, 2021. It is now read-only.
I am implementing the multi-tenancy via weave flux operators. My approach is the same, a cluster repo--> a cluster flux operator, and a namespace -> a namespace flux operator.
However, given that I do not want the flux operator be able to deleted or modified by mistakes by the namespace users, i decided to put all the namespace flux operators in the namesapce flux as below:
$ kubectl get pods -n flux
NAME READY STATUS RESTARTS AGE
demo2-flux-5c5f58f547-zvjb5 1/1 Running 0 5m23s
flux-6f6d459df5-jsqld 1/1 Running 0 9h
memcached-7b4c8bd545-5ks9g 1/1 Running 0 2d8h
demo2 is the namespace name, which I use the below to get it working
Obviously, in this case all the flux operators are sharing with one memcached services (pod).
My question is, what will be some of the considerations for working with one memcached services ?
The text was updated successfully, but these errors were encountered:
Hi,
I am implementing the multi-tenancy via weave flux operators. My approach is the same, a cluster repo--> a cluster flux operator, and a namespace -> a namespace flux operator.
However, given that I do not want the flux operator be able to deleted or modified by mistakes by the namespace users, i decided to put all the namespace flux operators in the namesapce flux as below:
demo2 is the namespace name, which I use the below to get it working
Obviously, in this case all the flux operators are sharing with one memcached services (pod).
My question is, what will be some of the considerations for working with one memcached services ?
The text was updated successfully, but these errors were encountered: