Updates to provider-kubeconfig.py to generate consumer kubeconfig #1376
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Also, modified provider-kubeconfig generator to include https in the provided API server IP only if it is not already present.
In the original design, we were using the output of kubectl connections to find out the Pods and then running metrics and logs on those Pods. However, for workloads in which Pods get created at runtime, connections is not able to find all the newly created workload Pods. This leads to incomplete results for metrics and logs. A simple way to handle this is to use all the pods in the namespace in which the application pods are running for collecting logs and metrics. The runtime Pods are typically created in the same namespace in which the application is running. This will give accurate results (atleast more accurate than using the output of kubect connections for the list of Pods). Fixes: #1190
Merge branch 'master' into develop
Fixes: #1208
Service name check
Added a field ('error') to the status object.
This is used by helmer to store any errors that
are encountered when performing helm upgrade.
It provides a UI for managing application instances. But it does not run on the cluster. The open-source equivalent is consumerUI, which is deployed as part KubePlus deployment.
Fixes: #1222
- Added link to Contributing guidelines. These guidelines contain pointer to setting up development environment - Extracted Architecture in a separate section - Updated link to CNCF Application definition section - Added Getting Started section Fixes: #1221
Licensing support
Correctly updating the status field of the CR instance upon app update
Moved KubePlus CRDs (ResourceComposition, etc.) in crds folder inside the chart. This ensures that the CRDs don't get deleted when KubePlus is upgraded. This further ensures that the application CRDs and application instances are not deleted when KubePlus is upgraded. Fixes: #1338
Fixes: #1355
- GH action runner on Kind seems to be having some issues. KubePlus Pod is not starting up. - Hence, re-added GH action on Minikube
In local testing on Minikube, one of the application Pods created as part of this test gets stuck in Pending state because of the need for more memory. It is possible that in the CI run in GH action this is happening as well. So skipping this test for now. We can turn it back on once we know exactly how much memory to use when creating local cluster for this test to pass. Also, in the spot check test with WordPress, okaying the test even if application Pods are in "Pending" state. Purpose of the spot check is to quickly verify the core functionality. For this, it is okay if application Pods are in Pending state (and don't progress to Running state). All we are interested in the Pods getting created, not whether they transition to the Running state.
- Enabling run on minikube on pull_request
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.