Nginx is a powerful, open-source web server and reverse proxy software. To deploy this app by deploying it as a workload, follow the procedure below.

Procedure

1. Go to EonKube > Advanced > Workloads..
2. In the top right-hand corner, click Create.
3. For the workload type, choose Deployments.
4. Specify the following settings:
   • Namespace: Choose a namespace.
   • Name: Specify an identifying name. For example, runner-workload.
   • (Optional) Description: If needed, specify the description.
   • Replicas: Choose the number of replicas. For example, when choosing 3, this means the workload will have three copies to run.
5. For the Container-0 settings, specify the following information:
   • Container Image: Specify nginxinc/nginx-unprivileged
   • Pull Policy: Select IfNotPresent.
6. For the networking settings, click Add Port or Service:
7. For the service type, choose one of the following based on your needs: Do not create a service, Cluster IP, Node Port, or Load Balancer.
   Choose Do not create a service to specify the default port of the pod(s), ex: input 8080 for Private Container Port, select TCP for Protocol When choosing Cluster IP, the application is exposed internally within the cluster and is not accessible from outside. Choose this service type if the application does not serve external access.
   When choosing Node Port, specify the following settings:
   • Name: Specify nginx-svc.
   • Private Container Port: Specify 80.
   • Protocol: Select TCP.
   When choosing Load Balancer, specify the following settings:
   • Name: Specify nginx-lb.
   • Private Container Port: Specify 80.
   • Protocol: Select TCP.
8. On the left panel, click Security Context and specify the following settings:
   • Privileged: Select No.
   • Privilege Escalation: Select No.
   • Run as Non-Root: Default No, select Yes when container must run as a non-root user.
   • Read-Only Root Filesystem: Default No, select Yes when container has read-only root filesystem.
9. On the mid panel, click Pod.
10. On the left panel, click Labels & Annotations, click Add Label to add key/value pairs to pods of the workload, ex: app=runner
11. On the left panel, click Node Scheduling and choose the way for the pod to operate:
    • When choosing Run pods on any available node, the pod will be scheduled on any available node.
    • When choosing Run pods on specific node(s), the pod will be scheduled on the node that you select. Choose a node for this pod to run.
    • When choosing Run pods on node(s) matching scheduling rules, the pod will be scheduled on any node that matches the rules you configure. To configure a rule, click Add Node Selector. Choose the priority of this rule and click Add Rule to specify the rule.
12. On the mid panel, click Deployment.
13. On the left panel, click Scaling and Upgrade Policy and choose the scaling and upgrade strategy for the pod.
    If needed, change the parameters when selecting the strategy. For Max Surge, it defines the maximum number of pods created above the desired number. For Max Unavailable, it defines how many pods can be unavailable during an update.
14. On the left panel, click Labels & Annotations and add identifying attributes:
    • Labels: Add a key/value pair for identification, ex: app=runner
    • Annotations: Add a key/value pair to include additional metadata.
15. Click Create.