![]() serviceaccount=some-namespace:mycluster-server Kubectl create rolebinding rabbitmq-mycluster:psp:unprivileged \ # role "rabbitmq:psp:unprivileged" created Kubectl create role rabbitmq:psp:unprivileged \ # Assuming RabbitmqCluster name is 'mycluster' In order to allow a Service Account to use PSPs, a Role with the verb 'use' mustīe bound to the Service Account. 'mycluster' will generate a Service Account named mycluster-server. The Operator creates a Service Account using the pattern INSTANCE-NAME-server. It's ok to create a binding that refers to a non-existing The Role and RoleBinding should be created before a RabbitmqCluster instance is created. If Pod security policies are not enabled, skip to Create a RabbitMQ Instance below. If Role and RoleBinding are used, it will only be effective in the Namespace where the RBACs are deployed. ![]() For more information about Pod security policies, If pod security policies are enabled in the Kubernetes cluster,Ī Role and RoleBinding must be created to enable the Pods to be scheduled. If it is not, install it by following the steps in the installation guide. Then verify that is on the list, as in the example below: ![]() To your Kubernetes cluster and is available. Confirm Service Availabilityīefore configuring your app to use RabbitMQ Cluster Kubernetes Operator, ensure that RabbitmqCluster Custom Resource is deployed Using the RabbitMQ Kubernetes Operators on Openshift.
0 Comments
Leave a Reply. |