Services and Discovery are the communication hub of your cluster. Think of it like a subway system within your cluster. The communications hub consists of three parts:
Ingress acts as a traffic light to direct the routing of services within the cluster through HTTP and HTTPS routes from outside the cluster. Defined rules tell the Ingress which routes to use for a given service.
The Ingress page is blank until an app is deployed. Once an app is deployed, you’ll see the: - Name, - Type, - Service, - Hosts, - Address (if applicable), - Number of Ports, - Age, - and Labels.
Critical Stacks creates in an Ingress in a few clicks. You can create an Ingress using the Simple form or the Command Line Tool (Advanced).
Simple 1. Click the Create Ingress button. 2. Select Simple. 3. The Create Ingress form opens. 4. Type an Ingress Name. 5. Select the Name of Service from the drop-down menu. 6. Assign a Port Number. 7. Select a TLS Secret from the drop-down menu, if necessary. 8. Click Save.
1. Click the Create Ingress button.
2. Select Advanced.
3. The Advanced Editor opens.
4. Complete the
5. Click Create.
6. Click OK.
The newly created Ingress appears in the list and the Ingress counter increases by 1.
Services provide the access to a set of Pods through policies. The Critical Stack UI provides a means to view the Services running on your cluster.
To create a new Service use the Create a New Service form or the Advanced Editor. Before you create a service, you’ll need to have a Pod or Deployment ready to use.
The new service appears in the Services list. Notice the Services counter went up by 1.
Endpoints are a list of IP addresses and Ports assigned to Services within the cluster.
The new endpoint appears at the top of the list.