We couldn't load the project sidebar. Refresh the page to try again.
If the problem persists, contact your Jira admin.

    • Icon: Sub-task Sub-task
    • Resolution: Fixed
    • Icon: L3 - Default L3 - Default
    • 3.10.0-alpha2, 3.10.0
    • None
    • None
    • None
    • Not defined

      As part of supporting OpenShift as a deployment target for our Helm charts, we need to ensure that our Docker images can run with arbitrary users. While there's a little more to cover than this, ensuring rootless/arbitrary user deployments covers the main source of issues with using the image in an OpenShift deployment.

      The goal here is simply to guarantee we have some smoke test which runs in our CI, allowing us to detect as early as possible if we were to break these guarantees.

      Acceptance criteria should be:

      A smoke test is added, running on every PR/merge as part of the CI pipeline, which tests the latest container image deployed using an arbitrary user ID (1000620000) and the root group ID (0).

      For context, here are the equivalent issue and PR on the Zeebe side.

        This is the controller panel for Smart Panels app

            Loading...

              • Icon: Sub-task Sub-task
              • Resolution: Fixed
              • Icon: L3 - Default L3 - Default
              • 3.10.0-alpha2, 3.10.0
              • None
              • None
              • None
              • Not defined

                As part of supporting OpenShift as a deployment target for our Helm charts, we need to ensure that our Docker images can run with arbitrary users. While there's a little more to cover than this, ensuring rootless/arbitrary user deployments covers the main source of issues with using the image in an OpenShift deployment.

                The goal here is simply to guarantee we have some smoke test which runs in our CI, allowing us to detect as early as possible if we were to break these guarantees.

                Acceptance criteria should be:

                A smoke test is added, running on every PR/merge as part of the CI pipeline, which tests the latest container image deployed using an arbitrary user ID (1000620000) and the root group ID (0).

                For context, here are the equivalent issue and PR on the Zeebe side.

                  This is the controller panel for Smart Panels app

                        Unassigned Unassigned
                        nicolas.pepin-perreault Nicolas Pepin-Perreault
                        Votes:
                        0 Vote for this issue
                        Watchers:
                        2 Start watching this issue

                          Created:
                          Updated:
                          Resolved:

                              Unassigned Unassigned
                              nicolas.pepin-perreault Nicolas Pepin-Perreault
                              Votes:
                              0 Vote for this issue
                              Watchers:
                              2 Start watching this issue

                                Created:
                                Updated:
                                Resolved: