You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@submarine.apache.org by "Kai-Hsun Chen (Jira)" <ji...@apache.org> on 2021/06/29 16:19:00 UTC
[jira] [Resolved] (SUBMARINE-804) Modify the apiGroup field in
rbac.yaml
[ https://issues.apache.org/jira/browse/SUBMARINE-804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kai-Hsun Chen resolved SUBMARINE-804.
-------------------------------------
Resolution: Fixed
Issue resolved by pull request 565.
Link: https://github.com/apache/submarine/pull/565
> Modify the apiGroup field in rbac.yaml
> --------------------------------------
>
> Key: SUBMARINE-804
> URL: https://issues.apache.org/jira/browse/SUBMARINE-804
> Project: Apache Submarine
> Issue Type: Task
> Reporter: Kai-Hsun Chen
> Assignee: Kai-Hsun Chen
> Priority: Trivial
> Labels: pull-request-available
> Fix For: 0.6.0
>
>
> As shown in [rbac.yaml:83|https://github.com/apache/submarine/blob/2faebb8efd69833853f62d89b4f1fea1b1718148/helm-charts/submarine/templates/rbac.yaml#L83], the value of apiGroup is "".
> However, the value of apiGroup in all of the following examples is "rbac.authorization.k8s.io".
> * Ref1: [Kubernetes official guide|https://kubernetes.io/docs/reference/access-authn-authz/rbac/#clusterrolebinding-example]
> * Ref2: [kube-lego|https://github.com/jetstack/kube-lego/blob/master/examples/gce/lego/cluster-role-binding.yaml] (Github Star: 2.2k)
> * Ref3: [redis-operator|https://github.com/spotahome/redis-operator/blob/b3dad57f5c4c94fe48824deacf391ab82232b3d5/charts/redisoperator/templates/rbac.yaml#L100] (Github Star: 672)
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@submarine.apache.org
For additional commands, e-mail: dev-help@submarine.apache.org