- Refactored ports and protocols info under docs/reference
- Updated the ports for kube-scheduler and kube-controller based on
current state
Co-authored-by: Tim Bannister <tim@scalefactory.com>
Apstra AOS (now owned by Juniper) has no direct integration with Kubernetes.
No CNI, no operator, no CRDs, nothing.
Kubernetes is not natively supported in the product, there is no mention of any k8s construct in the product.
This entry should be removed because it does not follow https://github.com/kubernetes/website/issues/20232
* Update docs to reflect newly support shells with autocompletions
* Update Windows docs to use Powershell instead of zsh
* Adds a bit more explanation of the different lines.
* Apply suggestions from code review
Co-authored-by: Tim Bannister <tim@scalefactory.com>
* Apply PR suggestions
Co-authored-by: Tim Bannister <tim@scalefactory.com>
The Service Catalog architecture changed from using api aggregation to CRDs, but the docs still refer to the older architecture using api aggregation.
Couple of changes here:
1. Change the sentence on how Service Catalog is implemented
2. Replace the example for usage of api aggregation from service-catalog to metrics-server. There are multiple implementations that can be linked to(keda, prometheus, datadog,...), but keeping the documentation neutral by pointing to kubernetes-sigs/metrics-server
References:
- Service Catalog [v0.3.0 release notes](https://github.com/kubernetes-sigs/service-catalog/releases/tag/v0.3.0):
> In release 0.3.0, we've focused on replacing the Aggregated API Server with the CustomResourceDefinitions (CRDs) and the Admission Webhook solution.
- Project [README](https://github.com/kubernetes-sigs/service-catalog/pull/2691/files)
> Service Catalog recently switched to a new CRDs-based architecture. The old API Server-based implementation is available on the v0.2 branch. We support this implementation by providing bug fixes until July 2020.
The interpretation between Docker and Kubernetes varies when comparing
its implementations. This allows different use cases and should be
documented accordingly.
Signed-off-by: Sascha Grunert <sgrunert@redhat.com>
Co-authored-by: Geoffrey Cline <gcline@amazon.com>
Signed-off-by: Sascha Grunert <sgrunert@redhat.com>
* Update English version of controlling-access.md as --insecure-port flag deprecated
* Update controlling-access.md as --insecure-port flag deprecated
* Update content/en/docs/concepts/security/controlling-access.md
Co-authored-by: Qiming Teng <tengqm@outlook.com>
Co-authored-by: Qiming Teng <tengqm@outlook.com>
Stephen Augustus