[K8SPXC64] OPENSHIFT INSTRUCTIONS FOR PXC OPERATOR MISS INSTRUCTIONS FOR

[K8SPXC-64] Openshift instructions for PXC operator miss instructions for ssl-secrets.yaml Created: 01/Nov/19  Updated: 23/Apr/20  Resolved: 15/Jan/20

Status:

Done

Project:

Percona Kubernetes Operator for Percona XtraDB Cluster

Component/s:

None

Affects Version/s:

1.2.0

Fix Version/s:

1.4.0

Type:

Bug

Priority:

Medium

Reporter:

Sveta Smirnova

Assignee:

Ivan Pylypenko

Resolution:

Cannot Reproduce

Votes:

0

Labels:

None

Remaining Estimate:

6 hours, 30 minutes

Time Spent:

5 hours

Original Estimate:

6 hours, 30 minutes

Attachments:

cr.yaml     crd.yaml     operator.logs    

Instructions at https://www.percona.com/doc/kubernetes-operator-for-pxc/openshift.html miss a step to deploy deploy/ssl-secrets.yaml However, if not deployed, cluster fails to start due to missed my-cluster-ssl secret

Comment by Mykola Marzhan [ 03/Nov/19 ]

Sveta Smirnova, which version of operator do you use?
it is an optional step, TLS should be generated by operator automatically if not applied.

Comment by Sveta Smirnova [ 03/Nov/19 ]

It is in the version field: PXC 1.2.0

Comment by Sveta Smirnova [ 04/Nov/19 ]

cr.yaml and crd.yaml are the default from the Github, version 1.2.0

Comment by Sveta Smirnova [ 04/Nov/19 ]

Operator logs attached

Comment by Ivan Pylypenko [ 12/Dec/19 ]

Sveta Smirnova Can't reproduce the issue. my-cluster-ssl files are created as it supposed to.

Have you followed the fifth paragraph ( cert-manager )?

Comment by Sveta Smirnova [ 08/Jan/20 ]

No, I am using default ones for testing purpose.

Comment by Sveta Smirnova [ 15/Jan/20 ]

The bug is not repeatable anymore:

sveta@Delly:~$ oc login -u system:admin
Logged into "https://192.168.42.12:8443" as "system:admin" using existing credentials.

You have access to the following projects and can switch between them with 'oc project <projectname>':

    default
    kube-dns
    kube-proxy
    kube-public
    kube-system
  * myproject
    openshift
    openshift-apiserver
    openshift-controller-manager
    openshift-core-operators
    openshift-infra
    openshift-node
    openshift-service-cert-signer
    openshift-web-console

Using project "myproject".
sveta@Delly:~/src/percona-xtradb-cluster-operator$ oc apply -f deploy/crd.yaml
customresourcedefinition.apiextensions.k8s.io/perconaxtradbclusters.pxc.percona.com created
customresourcedefinition.apiextensions.k8s.io/perconaxtradbclusterbackups.pxc.percona.com created
customresourcedefinition.apiextensions.k8s.io/perconaxtradbclusterrestores.pxc.percona.com created
customresourcedefinition.apiextensions.k8s.io/perconaxtradbbackups.pxc.percona.com created
sveta@Delly:~/src/percona-xtradb-cluster-operator$  oc create clusterrole pxc-admin --verb="*" --resource=perconaxtradbclusters.pxc.percona.com,perconaxtradbclusters.pxc.percona.com/status,perconaxtradbclusterbackups.pxc.percona.com,perconaxtradbclusterbackups.pxc.percona.com/status,perconaxtradbclusterrestores.pxc.percona.com,perconaxtradbclusterrestores.pxc.percona.com/status
clusterrole.rbac.authorization.k8s.io/pxc-admin created
sveta@Delly:~/src/percona-xtradb-cluster-operator$ oc adm policy add-cluster-role-to-user pxc-admin sveta
Warning: User 'sveta' not found
cluster role "pxc-admin" added: "sveta"
sveta@Delly:~/src/percona-xtradb-cluster-operator$ oc create clusterrole cert-admin --verb="*" --resource=issuers.certmanager.k8s.io,certificates.certmanager.k8s.io
the server doesn't have a resource type "issuers" in group "certmanager.k8s.io"
sveta@Delly:~/src/percona-xtradb-cluster-operator$ id
uid=1000(sveta) gid=1000(sveta) groups=1000(sveta),4(adm),24(cdrom),27(sudo),30(dip),46(plugdev),119(lpadmin),130(lxd),131(sambashare),136(libvirt),998(docker)
sveta@Delly:~/src/percona-xtradb-cluster-operator$ oc new-project pxc
Now using project "pxc" on server "https://192.168.42.12:8443".

You can add applications to this project with the 'new-app' command. For example, try:

    oc new-app centos/ruby-25-centos7~https://github.com/sclorg/ruby-ex.git

to build a new example application in Ruby.
sveta@Delly:~/src/percona-xtradb-cluster-operator$ oc apply -f deploy/rbac.yaml
role.rbac.authorization.k8s.io/percona-xtradb-cluster-operator created
serviceaccount/percona-xtradb-cluster-operator created
rolebinding.rbac.authorization.k8s.io/service-account-percona-xtradb-cluster-operator created
sveta@Delly:~/src/percona-xtradb-cluster-operator$ oc apply -f deploy/operator.yaml
deployment.apps/percona-xtradb-cluster-operator created
sveta@Delly:~/src/percona-xtradb-cluster-operator$ oc apply -f deploy/secrets.yaml
secret/my-cluster-secrets created
sveta@Delly:~/src/percona-xtradb-cluster-operator$ oc apply -f deploy/cr.yaml
perconaxtradbcluster.pxc.percona.com/cluster1 created
sveta@Delly:~/src/percona-xtradb-cluster-operator$ oc get pods
NAME                                               READY     STATUS              RESTARTS   AGE
percona-xtradb-cluster-operator-65c96d9fbb-f52kn   0/1       ContainerCreating   0          32s

Comment by Sveta Smirnova [ 15/Jan/20 ]

Either previous try was with developer user, not properly set in the Minishift or the issue fixed with the latest updates.