-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
[Connectedk8s] Kubernetes distro and infra parameter and heuristics support #2620
Conversation
…into distro-infra-feature
…into distro-infra-feature
If this PR is for a new extension or change to an existing extension, use the following to try out the changes in this PR:
|
from azure.cli.core.commands.parameters import (file_type) | ||
from azure.cli.core.commands.validators import get_default_location_from_resource_group | ||
|
||
distribution_types = ["auto", "generic", "openshift", "rancher_RKE", "kind", "GKE", "EKS", "AKS", "AKS-HCI", "CAPZ", "AKS-engine", "TKG"] | ||
infrastructure_types = ["auto", "generic", "azure", "AWS", "GCP", "Azure_Stack_HC", "Azure_Stack_Hub", "Azure_Stack_Edge", "vSphere"] | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"auto" is default cli value, which triggers heuristics evaluation, Remaining are the enum values.
@@ -6,6 +6,8 @@ | |||
|
|||
# pylint: disable=line-too-long | |||
|
|||
infrastructure_types = ["generic", "azure", "AWS", "GCP", "Azure_Stack_HC", "Azure_Stack_Hub", "Azure_Stack_Edge", "vSphere"] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Use following values:
- generic
- Amazon Web Services
- Google Cloud Platform
- Microsoft Azure
- Azure Stack Edge
- Azure Stack Hub
- Azure Stack HCI
- VMware vSphere
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
vSphere I'll check if we can differentiate between 6.x and 7.x by heuristics
from azure.cli.core.commands.parameters import (file_type) | ||
from azure.cli.core.commands.validators import get_default_location_from_resource_group | ||
|
||
distribution_types = ["auto", "generic", "openshift", "rancher_RKE", "kind", "GKE", "EKS", "AKS", "AKS-HCI", "CAPZ", "AKS-engine", "TKG"] | ||
infrastructure_types = ["auto", "generic", "azure", "AWS", "GCP", "Azure_Stack_HC", "Azure_Stack_Hub", "Azure_Stack_Edge", "vSphere"] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Use following values:
- generic
- Amazon Web Services
- Google Cloud Platform
- Microsoft Azure
- Azure Stack Edge
- Azure Stack Hub
- Azure Stack HCI
- VMware vSphere
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One doubt, so if user is providing these values, he will have to type whole like "AmazonWebServices". Isn't it easy for user for type just --infrastructure AWS?. We can always add a logic wherever we want to display(like in portal) to transform from AWS to Amazon Web Services.
from azure.cli.core.commands.parameters import (file_type) | ||
from azure.cli.core.commands.validators import get_default_location_from_resource_group | ||
|
||
distribution_types = ["auto", "generic", "openshift", "rancher_RKE", "kind", "GKE", "EKS", "AKS", "AKS-HCI", "CAPZ", "AKS-engine", "TKG"] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Use following values:
- Azure Kubernetes Service
- Google Kubernetes Engine
- Amazon Elastic Kubernetes Service
- Rancher Kubernetes Engine
- OpenShift Kubernetes Distribution
- OpenShift Container Platform
- K3s
- kind
- minikube
- Cluster API Provider Azure
- AKS Engine
- Tanzu Kubernetes Grid
- Canonical Charmed Kubernetes
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should check if we can distinguish between OKD and OCP in above list.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Connectedk8s |
…into distro-infra-feature
…into distro-infra-feature
src/connectedk8s/azext_connectedk8s/vendored_sdks/operations/connected_cluster_operations.py
Show resolved
Hide resolved
@fengzhou-msft Review is done from the connectedk8s side. It is ready for checking in if you don't have any further reviews. |
@fengzhou-msft Gentle ping regarding this. |
This checklist is used to make sure that common guidelines for a pull request are followed.
General Guidelines
azdev style <YOUR_EXT>
locally? (pip install azdev
required)python scripts/ci/test_index.py -q
locally?For new extensions:
About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your PR is merged into master branch, a new PR will be created to update
src/index.json
automatically.The precondition is to put your code inside this repo and upgrade the version in the PR but do not modify
src/index.json
.