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

upgrade or re-install steps for new version #3147

Open
doddisam opened this issue Feb 28, 2024 · 4 comments
Open

upgrade or re-install steps for new version #3147

doddisam opened this issue Feb 28, 2024 · 4 comments
Labels

Comments

@doddisam
Copy link

Background

We already have 0.8.1 version running and want to go to latest version. Is there steps i need to follow ?

Action to take

We already have 0.8.1 version running and want to go to latest version. Is there steps i need to follow ?

Impact

We already have 0.8.1 version running and want to go to latest version. Is there steps i need to follow ?

Dev Notes

No response

@danail-branekov
Copy link
Member

Korifi ships a helm chart, therefore upgrading Korifi should be a matter of just running the helm command. Make sure to provide the same values (--set arguments) when running the command. You also need to change the url to the chart itself, latest is https://github.com/cloudfoundry/korifi/releases/download/v0.11.0/korifi-0.11.0.tgz

@doddisam
Copy link
Author

doddisam commented Mar 5, 2024

Thanks for the update.

Also as part of korifi 0.8.1, i had setup the contour version v1.25.2 without gateway api support. Now from the documentation the latest version 0.11.0 uses gateway api. How do i upgrade contour now ?

Should i just follow static or dynamic provisioning below steps ?

Contour is our ingress controller. Follow the static provisioning instructions from the Gateway API support guide to install the latest version. Note that as part of the Contour installation you have to create a gatewayclass with name $GATEWAY_CLASS_NAME:

kubectl apply -f - <<EOF
kind: GatewayClass
apiVersion: gateway.networking.k8s.io/v1beta1
metadata:
name: $GATEWAY_CLASS_NAME
spec:
controllerName: projectcontour.io/gateway-controller
EOF
This gatewayclass name is a parameter of the helm chart installing korifi. The helm chart is going to define a gateway that will be used for all korifi ingress traffic.

or

Follow the dynamic provisioning instructions from the Gateway API support guide to install the latest version.

Note that as part of the Contour installation you have to create a gatewayclass with name $GATEWAY_CLASS_NAME:
kubectl apply -f - <<EOF
kind: GatewayClass
apiVersion: gateway.networking.k8s.io/v1beta1
metadata:
name: $GATEWAY_CLASS_NAME
spec:
controllerName: projectcontour.io/gateway-controller
EOF
You DO NOT need to create a gateway as per the instructions. The Korifi helm chart defines a gateway that will be used for all korifi ingress traffic. The gateway will be created in the korifi-gateway namespace.

Once above is done i can run the helm with same parameters ?

@doddisam
Copy link
Author

doddisam commented Mar 5, 2024

or we can still upgrade to 0.11.0 without Gateway API implementation of contour ?

@danail-branekov
Copy link
Member

Korifi 0.11.0 does not support native contour anymore, i.e. switching contour to Gateway API is a prerequisite for an upgrade. Keep in mind that switching to the gateway API in contour requires a contour restart that might cause a short downtime while contour is back again.

Other than that, yes, just follow the instructions and make sure to add the networking.gatewayClass helm value set to contour

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: 🧊 Icebox
Development

No branches or pull requests

2 participants