关注微信公众号
第一手干货与资讯
加入官方微信群
获取免费技术支持
Rancher manages Kubernetes and makes it accessible for both new and power users alike. It extends the flexibility of Kubernetes by offering a powerful and intuitive user interface for interacting with the cluster, while still keeping full access to the cluster via traditional means.
If you already have manifests that you wish to deploy, you can drop them into the Rancher UI, and Rancher will deploy them for you. This gives you an easy way to deploy YAML copied from documentation, tutorials, or other users, without needing to first save it and then apply it via kubectl.
Once deployed, the YAML for any resource can be edited directly from within the UI, which gives you an extra way to deploy quickly and then extract the correct YAML for inline or offline editing or incorporation into a source code repository.
Launch any type of workload from the Rancher UI, from Deployments to StatefulSets and DaemonSets, to Jobs and CronJobs. Rancher’s UI adapts to the workload type and shows you only the fields necessary for your chosen type. This prevents common errors and lets you deploy workloads faster.
Rancher automatically creates Services for Pods which expose ports, shortening the time to deploy a workload. With full support for every Service type, Rancher will provision internal and external resources and keep them in sync with the Pod definition.
Rancher ships with the Nginx ingress controller, but if you prefer to use HAProxy or Traefik or another controller, it’s trivial to swap it out. You have the flexibility to use the load balancing configuration that works for you and your environment.
Whether you provision static persistent volumes or use StorageClasses to define a dynamic structure, Rancher’s UI keeps the configuration organized. Workloads only see available PersistentVolumes or unused PersistentVolumeClaims, which lets you quickly see what’s available or identify when a PersistentVolume that you thought was available has already been claimed. When defining PersistentVolumes, Rancher’s menu structure shows you the available types and then the fields necessary for the type you choose.
You can also deploy provisioners and map them to a StorageClass, which will make them available for downstream workloads to use.
Secrets and ConfigMaps are two powerful Kubernetes resources. Use Rancher to visually define and update both types, and then select how to map them into workloads: either as environment variables or volumes. Rancher handles all of the configuration and deployment, helping you to keep your workloads running and secure.
Rancher acts as a secure repository for your TLS certificates. When you create an Ingress, you can choose one or more certificates to assign to it. Rancher passes the certificate data to Kubernetes, and the communication between the Ingress and its consumers will be encrypted.
Storing certificates within Rancher keeps them safe. Users can deploy resources that use a certificate without being given a copy of the certificate and its private key. Once installed, a certificate’s private key is held securely by Rancher. It is never visible in the UI or API, and any change to the certificate can only be done by an administrator who knows the private key.
Rancher supports deployment from any public registry. If you also use private registries, you can load the authentication data into Rancher, and when you deploy workloads that use containers from a private registry, Rancher will securely pass the authentication information to Kubernetes for use when pulling the images.