Git Product home page Git Product logo

Comments (7)

sanbornick avatar sanbornick commented on September 17, 2024

Aggregate to admin, edit, and view? How should the roles get applied? Should that be automated? Should that be different if the operator is installed namespaced?

from eunomia.

Smiley73 avatar Smiley73 commented on September 17, 2024

I'm thinking about keeping it simple right now and providing an admin and view role. I created 2 basic ones and will submit them soon with my helm installer PR.

from eunomia.

sanbornick avatar sanbornick commented on September 17, 2024

Meant for human use or by the operator?

because any of the CRs should be managed via GitOps anyway.

Do you intend for a given CR the operator is operating on to manage itself? Or is that intended to be managed by an upstream CR? Former there's a bootstrapping problem, latter you've got an location/ownership issue.

from eunomia.

Smiley73 avatar Smiley73 commented on September 17, 2024

We already have a custom role (both cluster and namespace) for the operator itself. So this one is just intended for people access.
It could be owned by an upstream CR, but that adds a whole new set of issues. We need to first get some runtime on it to determine what the best ways of managing it will be. We might have to split this out into two different charts in the future, one that requires cluster-admin and one that doesn't.
I want to keep this simple for now, until we learn more.

from eunomia.

Smiley73 avatar Smiley73 commented on September 17, 2024

@sanbornick I thought of this and think we should separate it right now. It'll be a much more realworld-ish approach. Stay tuned for an updated PR...

from eunomia.

Smiley73 avatar Smiley73 commented on September 17, 2024

@sanbornick I added the role aggregation. It'll be part of the larger PR

from eunomia.

vinny-sabatini avatar vinny-sabatini commented on September 17, 2024

Friendly reminder to remove this block when this issue is figured out.

eunomia/examples/cluster/teams/platform/cluster-seed/templates/templates/team-seeds.yaml

Lines 68 to 83 in 176fd8f

---
# We need to remove this once issue #53 is figured out
# Otherwise the team SAs wont have enough access
kind: ClusterRoleBinding
apiVersion: rbac.authorization.k8s.io/v1
metadata:
name: eunomia-runner-{{ .seedNamespace }}
namespace: {{ .seedNamespace }}
subjects:
- kind: ServiceAccount
name: {{ .serviceAccountRef }}
namespace: {{ .seedNamespace }}
roleRef:
kind: ClusterRole
name: cluster-admin
apiGroup: rbac.authorization.k8s.io

from eunomia.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.