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

Bootstrap initial kgateway helm chart #10470

Merged
merged 4 commits into from
Jan 17, 2025

Conversation

timflannagan
Copy link
Member

Description

This commit introduces an initial install/helm/kgateway chart via the helm create bootstrap command and updates the gateway2 codegen bash script to generate CRDs and RBAC for this chart along with the legacy chart. Note: this chart is not functional at this point. Future PRs will iterate on this effort, expand this chart values & templates, make sure it can be deployed correctly, passes the conformance suite, etc.

In the short term, the plan is to migrate away from the legacy chart + publish this chart with goreleaser to GHCR.io before we cut our first release in this new project.

Related to #10443.

Initial task for the #10423 tracker.

Checklist:

  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have added tests that prove my fix is effective or that my feature works

Signed-off-by: timflannagan <timflannagan@gmail.com>
Signed-off-by: timflannagan <timflannagan@gmail.com>
Signed-off-by: timflannagan <timflannagan@gmail.com>
Signed-off-by: timflannagan <timflannagan@gmail.com>
@timflannagan timflannagan changed the title Add initial kgateway helm chart Bootstrap initial kgateway helm chart Jan 17, 2025
- `values.yaml`: default configuration values for the chart

Check the [Gloo Edge docs](https://docs.solo.io/gloo-edge/latest/installation/)
Check the [K8s Gateway docs](https://docs.solo.io/k8s-gateway/latest/installation/)
Copy link
Contributor

Choose a reason for hiding this comment

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

this link doesn't work

# This is the chart version. This version number should be incremented each time you make changes
# to the chart and its templates, including the app version.
# Versions are expected to follow Semantic Versioning (https://semver.org/)
version: 0.1.0
Copy link
Contributor

Choose a reason for hiding this comment

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

do we want 0.0.1? do we need to keep this in sync with the kgateway release version?

# incremented each time you make changes to the application. Versions are not expected to
# follow Semantic Versioning. They should reflect the version the application is using.
# It is recommended to use it with quotes.
appVersion: "1.16.0"
Copy link
Contributor

Choose a reason for hiding this comment

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

do we need appVersion? how will it differ from version?

@@ -0,0 +1,22 @@
1. Get the application URL by running these commands:
Copy link
Contributor

Choose a reason for hiding this comment

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

do we need this file?

{{- else -}}
apiVersion: extensions/v1beta1
{{- end }}
kind: Ingress
Copy link
Contributor

Choose a reason for hiding this comment

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

do we need this file?

@@ -0,0 +1,28 @@
{{- if .Values.autoscaling.enabled }}
apiVersion: autoscaling/v2beta1
kind: HorizontalPodAutoscaler
Copy link
Contributor

Choose a reason for hiding this comment

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

do we need HPA for the control plane? afaik gloo only had that for the proxies but not control plane

@@ -0,0 +1,15 @@
apiVersion: v1
kind: Pod
Copy link
Contributor

Choose a reason for hiding this comment

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

do we need this?

@@ -0,0 +1,32 @@
---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
Copy link
Contributor

Choose a reason for hiding this comment

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

was a corresponding ClusterRoleBinding also generated?

@timflannagan
Copy link
Member Author

@jenshu I was going to rip out the non-helm-generated bits that aren't relevant here (e.g. ingress) in a follow-up, but I can do that here if you prefer.

@jenshu jenshu added this pull request to the merge queue Jan 17, 2025
Merged via the queue into kgateway-dev:main with commit 17dffbe Jan 17, 2025
5 checks passed
@timflannagan timflannagan deleted the chore/add-initial-chart branch January 17, 2025 21:24
timflannagan added a commit to timflannagan/kgateway that referenced this pull request Jan 21, 2025
This commit is a follow-up to kgateway-dev#10443 and kgateway-dev#10470 and migrates
away from the quay.io/solo-io container image registry in
favor of the ghcr.io repository in the project.

Additional work around renaming the gloo component, binaries, etc.
will be handled once we're closing the finish line with the

Signed-off-by: timflannagan <timflannagan@gmail.com>
tiberiuac pushed a commit to openet/gloo that referenced this pull request Feb 13, 2025
…ateway-dev#10470) (kgateway-dev#10496)

Backports 1bed380 from main

Signed-off-by: Shashank Ram <shashank.ram@solo.io>
stevenctl pushed a commit to stevenctl/gloo that referenced this pull request Feb 17, 2025
…ateway-dev#10470) (kgateway-dev#10497)

Backports 1bed380 from main.

Signed-off-by: Shashank Ram <shashank.ram@solo.io>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants