Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add basic chart for the new api-syncagent #121

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
Open

Conversation

xrstf
Copy link
Contributor

@xrstf xrstf commented Jan 9, 2025

This adds a simple chart to deploy an instance of https://github.com/kcp-dev/api-syncagent.

fixes #120

@kcp-ci-bot kcp-ci-bot added dco-signoff: yes Indicates the PR's author has signed the DCO. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Jan 9, 2025
charts/api-syncagent/templates/rbac.yaml Outdated Show resolved Hide resolved
charts/api-syncagent/templates/rbac.yaml Outdated Show resolved Hide resolved
charts/api-syncagent/templates/rbac.yaml Outdated Show resolved Hide resolved
charts/api-syncagent/templates/rbac.yaml Outdated Show resolved Hide resolved
charts/api-syncagent/templates/rbac.yaml Outdated Show resolved Hide resolved
charts/api-syncagent/templates/deployment.yaml Outdated Show resolved Hide resolved
@kcp-ci-bot
Copy link
Contributor

[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 ask for approval from embik. For more information see the Kubernetes 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:

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

This offered no real benefit over someone simply having their own
rbac.yaml. Adding this as an option to the chart just means we
have to continue to support it, and why would we then only support
defining custom RBAC and not even other resources? At that point we
would become a meta-meta Helm chart and that's just not worth it.

On-behalf-of: @SAP [email protected]
@xrstf xrstf force-pushed the add-api-syncagent branch from 47173e6 to f5a4c48 Compare January 10, 2025 11:25
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
name: '{{ template "name" . }}:{{ .Release.Namespace }}'
Copy link
Member

Choose a reason for hiding this comment

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

I think this is now missing RBAC for publishedresources.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dco-signoff: yes Indicates the PR's author has signed the DCO. 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.

feature: create Helm chart for kcp-dev/api-syncagent
3 participants