Uploaded image for project: 'Red Hat Advanced Cluster Security'
  1. Red Hat Advanced Cluster Security
  2. ROX-24956

roxctl sensor generate does not respect admission controller timeout settings

    • Icon: Task Task
    • Resolution: Won't Do
    • Icon: Undefined Undefined
    • None
    • None
    • Helm Install
    • 0
    • Customer Facing

      USER PROBLEM

      I have noticed that roxctl does not respect admission controller settings for the `sensor generate` command. For example:

      $ roxctl -e "$CENTRAL_ENDPOINT" sensor generate k8s --name=foo --admission-controller-timeout=6

      produces a deployment bundle for a secured-cluster named "foo", but the `timeoutSeconds` field in the manifest `sensor-foo/admission-controller.yaml` does not contain the configured timeout.

      It looks like this is caused by roxctl/sensor/generate.go, line 187.

      In the end the generated manifests will contain a default timeout coming from central.

      CONDITIONS
      What conditions need to exist for a user to be affected? Is it everyone? Is it only those with a specific integration? Is it specific to someone with particular database content? etc.

      • pending

      ROOT CAUSE
      What is the root cause of the bug?

      • pending

      FIX
      How was the bug fixed (this is more important if a workaround was implemented rather than an actual fix)?

      • pending

              mclasmei@redhat.com Moritz Clasmeier
              mclasmei@redhat.com Moritz Clasmeier
              Moritz Clasmeier
              ACS Install
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: