Knative FAQ

Changing a value in config-defaults configmap would immediatly impact the ksvc?

Yes, changing a value in the config-defaults configmap would immediately impact the Knative services that are using that configmap. This is because Knative services are constantly watching the config-defaults configmap for changes. When a change is detected, the Knative service will automatically update its configuration to reflect the change.

For example, if you change the container concurrency value in the config-defaults configmap to 10, any Knative services that are using that configmap will immediately be scaled up to 10 pods.

It is important to note that changing a value in the config-defaults configmap can have a significant impact on the performance and scalability of your Knative services. It is important to test any changes to the config-defaults configmap in a staging environment before making them to your production environment.

When i upgrade knative component, Would my ksvc would be deleted?

No, your ksvc will not be deleted when you upgrade knative components. However, if the upgrade changes the configuration of your ksvc, you may need to make some manual changes to your ksvc manifest to ensure that it continues to function correctly.

Can i upgrade knative from 1.0.0 to 1.10.0 directly

No, you cannot upgrade Knative from 1.0.0 to 1.10.0 directly. There are a few intermediate versions that you need to upgrade to in between. The recommended upgrade path is as follows:

1. Upgrade to Knative 1.1.0
2. Upgrade to Knative 1.2.0
3. Upgrade to Knative 1.3.0
4. Upgrade to Knative 1.4.0
5. Upgrade to Knative 1.5.0
6. Upgrade to Knative 1.6.0
7. Upgrade to Knative 1.7.0
8. Upgrade to Knative 1.8.0
9. Upgrade to Knative 1.9.0
10. Upgrade to Knative 1.10.0

You can find the upgrade instructions for each version of Knative on the Knative documentation website.

Here are some reasons why you cannot upgrade Knative directly from 1.0.0 to 1.10.0:

• There are breaking changes between some versions of Knative. These breaking changes can cause your Knative components to stop working correctly if you upgrade directly.
• The upgrade process for Knative is designed to be gradual. This allows you to test each upgrade step and make sure that your Knative components are still working correctly before you move on to the next step.

Rajesh Kumar

I’m Rajesh Kumar, a DevOps, SRE, DevSecOps, Cloud, and Platform Engineering expert passionate about sharing practical knowledge, real-world experiences, and industry best practices. I have worked at Cotocus and regularly write about technology, travel, investing, health, product reviews, and digital marketing through my various platforms.

I publish technical articles at DevOps School, travel stories at Holiday Landmark, stock market insights at Stocks Mantra, health and fitness guidance at My Medic Plus, product reviews at TrueReviewNow, and SEO and digital marketing strategies at Wizbrand.