Skip to content
This repository was archived by the owner on Sep 21, 2023. It is now read-only.
This repository was archived by the owner on Sep 21, 2023. It is now read-only.

no-op after creation of the CRD on openshift 3.10 #351

@jayunit100

Description

@jayunit100

On openshift (3.10), i see no resources created after i make the vault CRD.

  • The vault operator is healthy:
➜  vault-operator git:(openshift) ✗ oc get pods --all-namespaces | grep vau
vault                               vault-operator-694f678549-x6jb4                       1/1       Running            0          1h
  • The logs when creating a CRD, look like this:
ERROR: logging before flag.Parse: I1010 17:12:13.892378       1 leaderelection.go:184] successfully acquired lease vault/vault-operator
time="2018-10-10T17:12:13Z" level=info msg="Event(v1.ObjectReference{Kind:\"Endpoints\", Namespace:\"vault\", Name:\"vault-operator\", UID:\"a1fa7cf5-ccaf-11e8-b49a-005056b9215d\", APIVersion:\"v1\", ResourceVersion:\"1628479\", FieldPath:\"\"}): type: 'Normal' reason: 'LeaderElection' vault-operator-694f678549-x6jb4 became leader"
time="2018-10-10T17:12:13Z" level=info msg="starting Vaults controller"
ERROR: logging before flag.Parse: W1010 17:28:12.478461       1 reflector.go:334] github.com/coreos-inc/vault-operator/pkg/operator/controller.go:35: watch of *v1alpha1.VaultService ended with: The resourceVersion for the provided watch is too old.

Creating new CRD's after this point doesnt seem to lead to any log messages. Not sure why.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions