Skip to content

Create a ServiceAccount for Broker Ingress#1241

Merged
knative-prow-robot merged 4 commits into
knative:masterfrom
Harwayne:ingress-sa
May 20, 2019
Merged

Create a ServiceAccount for Broker Ingress#1241
knative-prow-robot merged 4 commits into
knative:masterfrom
Harwayne:ingress-sa

Conversation

@Harwayne
Copy link
Copy Markdown
Contributor

Helps with #704, as this SA will be needed to get ConfigMap reading permissions.

Proposed Changes

  • Use the Service Account eventing-broker-ingress, rather than default on Broker Ingress Pods.
  • Create the Service Account via the namespace annotation.
  • Add the instructions to create the Service Account manually for those that don't use the annotation.

Release Note

If you are using a Broker in a namespace not annotated with eventing injection, then you will need to follow the [manual setup instructions](https://github.com/knative/eventing/tree/master/docs/broker#manual-setup) to create the required ServiceAccount and RoleBinding. 

Note that failing to do so will not cause immediately noticable failures. Only after a subsequent PR starts watching ConfigMaps will the failure begin to manifest, in the form of crash looping Broker Ingress Pods.

@googlebot googlebot added the cla: yes Indicates the PR's author has signed the CLA. label May 15, 2019
@knative-prow-robot
Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Harwayne

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

The pull request process is described here

Details Needs approval from an approver in each of these files:

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

@knative-prow-robot knative-prow-robot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels May 15, 2019
@Harwayne
Copy link
Copy Markdown
Contributor Author

Ping.

brokerCreated = "BrokerCreated"
serviceAccountCreated = "BrokerFilterServiceAccountCreated"
serviceAccountRBACCreated = "BrokerFilterServiceAccountRBACCreated"
serviceAccountCreated = "BrokerServiceAccountCreated"
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

might be better to have the 4 events: BrokerFilterXXX and BrokerIngressXXX, and you pass them as args when you call the method?
But I'm ok either way, if you want to leave it as is, it's fine.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess with the message you are printing the name of the service account or role binding. We can leave it as is...

Comment thread docs/broker/README.md

In order to setup a `Broker` manually, we must first create the required
`ServiceAccount` and give it the proper RBAC permissions. This setup is required
`ServiceAccount`s and give them the proper RBAC permissions. This setup is required
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Now that you are editing this file... can you fix the cosmetic:

the implmentation may change at any time, absolutely no guarantees are made about the implmentation

Also, inside Implementation, Namespace, you will have to add the steps of creating the eventing-broker-filter service account, and the RBAC.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Now that is fresh, there is a broker_trigger.md file in knative/docs, with this manual steps as well. It'd be great if you can create a follow up PR on docs with this same changes...

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Made the changes here.

Once this gets in, I'll immediately open a PR on docs to update it their too.

Maybe we should just delete this file? And rely on docs only?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, I think it'd be better to remove this one. Just check if it has the same content. I think the docs one doesn't have the implementation, but I think it's fine to skip that section.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OK. In a follow up PR (after I submit the changes to docs), I'll pair this down to a link to docs and implementation details.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sounds good!

Comment thread pkg/reconciler/namespace/namespace.go Outdated
Comment thread pkg/reconciler/namespace/namespace.go Outdated
Comment thread pkg/reconciler/namespace/namespace.go Outdated
Comment thread pkg/reconciler/namespace/namespace.go Outdated
@knative-metrics-robot
Copy link
Copy Markdown

The following is the coverage report on pkg/.
Say /test pull-knative-eventing-go-coverage to re-run this coverage report

File Old Coverage New Coverage Delta
pkg/reconciler/namespace/namespace.go Do not exist 79.8%

@nachocano
Copy link
Copy Markdown
Contributor

/lgtm

@knative-prow-robot knative-prow-robot added the lgtm Indicates that a PR is ready to be merged. label May 20, 2019
@knative-prow-robot knative-prow-robot merged commit 3f8ecf9 into knative:master May 20, 2019
Harwayne added a commit to Harwayne/knative-docs that referenced this pull request May 20, 2019
knative-prow-robot pushed a commit to knative/docs that referenced this pull request May 21, 2019
@Harwayne Harwayne deleted the ingress-sa branch May 29, 2019 17:37
RichieEscarez pushed a commit to RichieEscarez/docs that referenced this pull request Jun 6, 2019
knative-prow-robot pushed a commit to knative/docs that referenced this pull request Jun 7, 2019
* pr#1408

* pr#1398

* service/samples: add .dockerignore to samples with local build disruption risk (#1392)

* service/samples: add .dockerignore to samples with risk of local build interference

* serving/samples: .dockerignore readme text update

* Update docs/serving/samples/hello-world/helloworld-csharp/README.md

Co-Authored-By: RichieEscarez <rescarez@google.com>

* Update docs/serving/samples/hello-world/helloworld-nodejs/README.md

Co-Authored-By: RichieEscarez <rescarez@google.com>

* Update docs/serving/samples/hello-world/helloworld-python/README.md

Co-Authored-By: RichieEscarez <rescarez@google.com>

* Update docs/serving/samples/hello-world/helloworld-php/README.md

Co-Authored-By: Evan Anderson <evan.k.anderson@gmail.com>

* Fix the wrong information in grpc example (#1380)

* pr#1363

* Fix samples path (#1357)

* Copy the updates from knative/eventing#1241. (#1355)

* add reference to custom DNS config (#1327)

* add reference to custom DNS config

* Update docs/install/getting-started-knative-app.md

Co-Authored-By: Sam O'Dell <31352624+samodell@users.noreply.github.com>

* fix relative link

* Fix PR#1202

* Document serving tag resolution (#1260)

Our controller does resolution of tags to digests, which has been a
source of confusion. This documents the fact that we do it, why we do
it, and how to configure the controller to work around common issues.
RichieEscarez pushed a commit to RichieEscarez/docs that referenced this pull request Jun 12, 2019
markusthoemmes pushed a commit to markusthoemmes/knative-eventing that referenced this pull request May 17, 2021
Signed-off-by: Matthias Wessendorf <mwessend@redhat.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. cla: yes Indicates the PR's author has signed the CLA. lgtm Indicates that a PR is ready to be merged. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants