✨ (hack) Make service-account optional

[perdasilva]

Description

• makes the olmv1 service account admin
• makes the .spec.serviceAccount optional
• sets create namespace to true in the helm applier

cat <<EOF | kubectl create -f -
apiVersion: olm.operatorframework.io/v1
kind: ClusterExtension
metadata:
  name: zookeeper-operator
spec:
  namespace: zookeeper-operator
  source:
    sourceType: Catalog
    catalog:
      packageName: zookeeper-operator
      version: 0.17.0

kubectl wait clusterextension zookeeper-operator --for=condition=Installed=true

Demo

Reviewer Checklist

• API Go Documentation
• Tests: Unit Tests (and E2E Tests, if appropriate)
• Comprehensive Commit Messages
• Links to related GitHub Issue(s)

[netlify]

✅ Deploy Preview for olmv1 ready!

Name	Link
🔨 Latest commit	f594f63
🔍 Latest deploy log	https://app.netlify.com/sites/olmv1/deploys/681c7c95a13e03000824c8b2
😎 Deploy Preview	https://deploy-preview-1956--olmv1.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign tmshort for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[camilamacedo86]

Would not it result in OLM have all possible permissions, do we want that?

[perdasilva]

that's an open question at the moment. But given that we can create tokens for any service account, that's essentially what we have already XDD

[camilamacedo86]

So, can we create one to bind if the user does not provide an SA?
Is that?

[perdasilva]

the point of this PR was just to demo the kind of UX I'm after. It just made it so that you could stamp out a ClusterExtension and everything would "just work". I didn't really think about all the odds and ends. I think the idea here was: if user doesn't specify an sa, just use olm's.