Skip to content

Commit

Permalink
Merge pull request #29 from triggermesh/task/update-manifests
Browse files Browse the repository at this point in the history
Task: update manifests
  • Loading branch information
Pablo Mercado committed Aug 28, 2023
2 parents 5ca17bd + fdaeaae commit c9d7d41
Show file tree
Hide file tree
Showing 21 changed files with 586 additions and 213 deletions.
16 changes: 9 additions & 7 deletions .github/workflows/build-and-release.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -21,12 +21,12 @@ jobs:
uses: actions/checkout@v3

- name: Set up Go
uses: actions/setup-go@v3
uses: actions/setup-go@v4
with:
go-version: '1.19'
go-version: '1.20'

- name: Go caches
uses: actions/cache@v2
uses: actions/cache@v3
with:
path: |
~/go/pkg/mod
Expand All @@ -49,12 +49,12 @@ jobs:
uses: actions/checkout@v3

- name: Set up Go
uses: actions/setup-go@v3
uses: actions/setup-go@v4
with:
go-version: '1.19'
go-version: '1.20'

- name: Go caches
uses: actions/cache@v2
uses: actions/cache@v3
with:
path: |
~/go/pkg/mod
Expand All @@ -79,6 +79,7 @@ jobs:
IMAGE_TAG=sha-${GITHUB_SHA:0:7}
[[ ${GITHUB_REF_TYPE} == "tag" ]] && IMAGE_TAG=${GITHUB_REF_NAME}
echo "IMAGE_TAG=${IMAGE_TAG}" >> $GITHUB_OUTPUT
echo "IMAGE_TAG=${IMAGE_TAG}"
- name: Publish container images
env:
Expand All @@ -87,6 +88,7 @@ jobs:
DIST_DIR: /tmp/dist
run: |
IMAGE_TAG=${{ steps.image-tag.outputs.IMAGE_TAG }} make release
echo "generated images with tag ${{steps.image-tag.outputs.IMAGE_TAG}}"
- name: Upload artifact
if: github.event_name == 'push' && contains(github.ref, 'refs/tags/')
Expand All @@ -104,7 +106,7 @@ jobs:
contents: write
steps:
- name: Checkout
uses: actions/checkout@v2
uses: actions/checkout@v3
with:
fetch-depth: 0

Expand Down
17 changes: 11 additions & 6 deletions .github/workflows/e2e-tests.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -23,9 +23,9 @@ jobs:
-d '{"state":"pending","target_url":"${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }}","context":"${{ github.workflow }}"}'
- name: Set up Go
uses: actions/setup-go@v3
uses: actions/setup-go@v4
with:
go-version: '1.19'
go-version: '1.20'

- name: Go caches
uses: actions/cache@v3
Expand All @@ -41,9 +41,9 @@ jobs:
uses: container-tools/kind-action@v2
with:
version: v0.13.0
knative_eventing: v1.4.0
knative_serving: v1.4.0
knative_kourier: v1.4.0
knative_eventing: v1.6.0
knative_serving: v1.6.0
knative_kourier: v1.6.0
# ko loads images directly into KinD's container runtime when
# KO_DOCKER_REPO is set to the rogue value "kind.local", so we have no
# use for a container registry.
Expand Down Expand Up @@ -90,15 +90,20 @@ jobs:
- name: Deploy TriggerMesh
run: |
echo "Image tag being used: ${{ github.event.client_payload.image_tag }}"
sed -i config/500-*.yaml \
-e "s|ko://github.com/triggermesh/triggermesh-event-sources-bundle/cmd/\(.*$\)|gcr.io/triggermesh/event-sources-bundle/\1:${{ github.event.client_payload.image_tag }}|g"
kubectl apply -f config/
kubectl -n triggermesh wait deployments.app --timeout=5m --for=condition=Available -l app.kubernetes.io/part-of=triggermesh
- name: Wait for TriggerMesh deployment
run: |
kubectl -n knative-serving wait deployments.app --timeout=5m --for=condition=Available -l app.kubernetes.io/name=knative-serving
kubectl -n knative-eventing wait deployments.app --timeout=5m --for=condition=Available -l app.kubernetes.io/name=knative-eventing
kubectl -n triggermesh get pods -l app.kubernetes.io/part-of=triggermesh
kubectl -n triggermesh wait deployments.app --timeout=5m --for=condition=Available -l app.kubernetes.io/part-of=triggermesh
- name: Install Ginkgo
run: go install github.com/onsi/ginkgo/v2/ginkgo

Expand Down
6 changes: 3 additions & 3 deletions .github/workflows/generated.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -13,15 +13,15 @@ jobs:
runs-on: ubuntu-latest

steps:
- uses: actions/checkout@v2
- uses: actions/checkout@v3

- name: Set up Go
uses: actions/setup-go@v2
uses: actions/setup-go@v4
with:
go-version: '1.20'

- name: Go caches
uses: actions/cache@v2
uses: actions/cache@v3
with:
path: |
~/go/pkg/mod
Expand Down
6 changes: 3 additions & 3 deletions .github/workflows/licenses.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -13,15 +13,15 @@ jobs:
runs-on: ubuntu-latest

steps:
- uses: actions/checkout@v2
- uses: actions/checkout@v3

- name: Set up Go
uses: actions/setup-go@v2
uses: actions/setup-go@v4
with:
go-version: '1.20'

- name: Go caches
uses: actions/cache@v2
uses: actions/cache@v3
with:
path: |
~/.cache/go-build
Expand Down
50 changes: 47 additions & 3 deletions config/300-awscloudwatchlogssource.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -117,6 +117,28 @@ spec:
oneOf:
- required: [value]
- required: [valueFromSecret]
sessionToken:
description: The AWS session token for temporary credentials.
type: object
properties:
value:
description: Literal value of the session token.
type: string
format: password
valueFromSecret:
description: A reference to a Kubernetes Secret object containing the session token.
type: object
properties:
name:
type: string
key:
type: string
required:
- name
- key
oneOf:
- required: [value]
- required: [valueFromSecret]
assumeIamRole:
description: |-
The ARN of an IAM role for cross-account or remote EKS cluster authorization.
Expand All @@ -127,14 +149,36 @@ spec:
- accessKeyID
- secretAccessKey
iamRole:
description: (Amazon EKS only) The ARN of an IAM role which can be impersonated to obtain AWS permissions.
For more information about IAM roles for service accounts, please refer to the Amazon EKS User Guide
at https://docs.aws.amazon.com/eks/latest/userguide/iam-roles-for-service-accounts.html
description: Deprecated, please use "iam" object instead.
type: string
pattern: ^arn:aws(-cn|-us-gov)?:iam::\d{12}:role\/.+$
iam:
description: The IAM role authentication parameters. For Amazon EKS only.

type: object
properties:
roleArn:
description: |-
The ARN of an IAM role which can be impersonated to obtain AWS permissions. For
more information about IAM roles for service accounts, please refer to the Amazon EKS User Guide
at https://docs.aws.amazon.com/eks/latest/userguide/iam-roles-for-service-accounts.html
Beware that this IAM role only applies to the receive adapter, for retrieving S3 notifications
from the intermediate Amazon SQS queue. The TriggerMesh controller requires its own set of IAM
permissions for interacting with the Amazon S3 and (optionally) Amazon SQS management APIs. These
can be granted via a separate IAM role, through the 'triggermesh-controller' serviceAccount that
is located inside the 'triggermesh' namespace.
type: string
pattern: ^arn:aws(-cn|-us-gov)?:iam::\d{12}:role\/.+$
serviceAccount:
description: |-
The name of the service account to be assigned on the receive adapter. Can be created externally and
shared between multiple components.
type: string
oneOf:
- required: [credentials]
- required: [iamRole]
- required: [iam]
sink:
description: The destination of events generated from Amazon CloudWatch Logs.
type: object
Expand Down
49 changes: 46 additions & 3 deletions config/300-awscloudwatchsource.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -176,6 +176,28 @@ spec:
oneOf:
- required: [value]
- required: [valueFromSecret]
sessionToken:
description: The AWS session token for temporary credentials.
type: object
properties:
value:
description: Literal value of the session token.
type: string
format: password
valueFromSecret:
description: A reference to a Kubernetes Secret object containing the session token.
type: object
properties:
name:
type: string
key:
type: string
required:
- name
- key
oneOf:
- required: [value]
- required: [valueFromSecret]
assumeIamRole:
description: |-
The ARN of an IAM role for cross-account or remote EKS cluster authorization.
Expand All @@ -186,14 +208,35 @@ spec:
- accessKeyID
- secretAccessKey
iamRole:
description: (Amazon EKS only) The ARN of an IAM role which can be impersonated to obtain AWS permissions.
For more information about IAM roles for service accounts, please refer to the Amazon EKS User Guide
at https://docs.aws.amazon.com/eks/latest/userguide/iam-roles-for-service-accounts.html
description: Deprecated, please use "iam" object instead.
type: string
pattern: ^arn:aws(-cn|-us-gov)?:iam::\d{12}:role\/.+$
iam:
description: The IAM role authentication parameters. For Amazon EKS only.
type: object
properties:
roleArn:
description: |-
The ARN of an IAM role which can be impersonated to obtain AWS permissions. For
more information about IAM roles for service accounts, please refer to the Amazon EKS User Guide
at https://docs.aws.amazon.com/eks/latest/userguide/iam-roles-for-service-accounts.html
Beware that this IAM role only applies to the receive adapter, for retrieving S3 notifications
from the intermediate Amazon SQS queue. The TriggerMesh controller requires its own set of IAM
permissions for interacting with the Amazon S3 and (optionally) Amazon SQS management APIs. These
can be granted via a separate IAM role, through the 'triggermesh-controller' serviceAccount that
is located inside the 'triggermesh' namespace.
type: string
pattern: ^arn:aws(-cn|-us-gov)?:iam::\d{12}:role\/.+$
serviceAccount:
description: |-
The name of the service account to be assigned on the receive adapter. Can be created externally and
shared between multiple components.
type: string
oneOf:
- required: [credentials]
- required: [iamRole]
- required: [iam]
sink:
description: The destination of events generated from Amazon CloudWatch metrics.
type: object
Expand Down
50 changes: 47 additions & 3 deletions config/300-awscodecommitsource.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -127,6 +127,28 @@ spec:
oneOf:
- required: [value]
- required: [valueFromSecret]
sessionToken:
description: The AWS session token for temporary credentials.
type: object
properties:
value:
description: Literal value of the session token.
type: string
format: password
valueFromSecret:
description: A reference to a Kubernetes Secret object containing the session token.
type: object
properties:
name:
type: string
key:
type: string
required:
- name
- key
oneOf:
- required: [value]
- required: [valueFromSecret]
assumeIamRole:
description: |-
The ARN of an IAM role for cross-account or remote EKS cluster authorization.
Expand All @@ -137,14 +159,36 @@ spec:
- accessKeyID
- secretAccessKey
iamRole:
description: (Amazon EKS only) The ARN of an IAM role which can be impersonated to obtain AWS permissions.
For more information about IAM roles for service accounts, please refer to the Amazon EKS User Guide
at https://docs.aws.amazon.com/eks/latest/userguide/iam-roles-for-service-accounts.html
description: Deprecated, please use "iam" object instead.
type: string
pattern: ^arn:aws(-cn|-us-gov)?:iam::\d{12}:role\/.+$
iam:
description: The IAM role authentication parameters. For Amazon EKS only.

type: object
properties:
roleArn:
description: |-
The ARN of an IAM role which can be impersonated to obtain AWS permissions. For
more information about IAM roles for service accounts, please refer to the Amazon EKS User Guide
at https://docs.aws.amazon.com/eks/latest/userguide/iam-roles-for-service-accounts.html
Beware that this IAM role only applies to the receive adapter, for retrieving S3 notifications
from the intermediate Amazon SQS queue. The TriggerMesh controller requires its own set of IAM
permissions for interacting with the Amazon S3 and (optionally) Amazon SQS management APIs. These
can be granted via a separate IAM role, through the 'triggermesh-controller' serviceAccount that
is located inside the 'triggermesh' namespace.
type: string
pattern: ^arn:aws(-cn|-us-gov)?:iam::\d{12}:role\/.+$
serviceAccount:
description: |-
The name of the service account to be assigned on the receive adapter. Can be created externally and
shared between multiple components.
type: string
oneOf:
- required: [credentials]
- required: [iamRole]
- required: [iam]
sink:
description: The destination of events sourced from Amazon CodeCommit.
type: object
Expand Down
Loading

0 comments on commit c9d7d41

Please sign in to comment.