Learning path for developers

Access the cluster

Begin working with your cluster by setting up the CLI and accessing the cluster.

1. CLI setup: Set up the CLIs that are necessary to create and work with clusters. As you work with your cluster, refer to the command reference and keep track of CLI version updates with the CLI change log.
2. User permissions: Ensure that your cluster administrator gives you the proper IBM Cloud IAM role to access the cluster.
3. Cluster access: Access your cluster through the public or private cloud service endpoint.

Need help? Check out Troubleshooting clusters and masters and Troubleshooting worker nodes.

Plan your deployment

Before you deploy an app, decide how you want to set up your app so that your app can be accessed properly and be integrated with other services.

1. Kubernetes-native: Plan your strategy for developing a Kubernetes-native app.
2. Highly available: Plan your strategy for a highly available deployment.

Looking for serverless? Try Code Engine.

Develop your app

Configure your app in a YAML file that declares the configuration of the Kubernetes object, and plan your app versioning strategy.

1. Develop your app:
   1. Review the basics of Kubernetes-native app deployments.
   2. Build app containers from images in the internal, public, or private registries.
   3. Specify your app requirements in a YAML file, which declares the configuration of the Kubernetes object.
2. Version your app:
   1. To plan customized configurations for more than one environment, such as development, testing, and production environments, use the Kustomize tool to manage your configuration YAML file.
   2. If you want to run your app in multiple clusters, public and private environments, or even multiple cloud providers, package your application to help automate deployments.

Need help? Check out Troubleshooting apps and integrations.

Deploy your app

Deploy your app to the cluster by running your app configuration file.

• Deploying apps with the Kubernetes dashboard.
• Deploying apps with the CLI.
• Deploying apps to specific worker nodes by using labels.
• Deploying an app on a GPU machine.

Need help? Check out Troubleshooting apps and integrations.

Test, log, and monitor

While you conduct performance testing on your app, set up logging and monitoring to help you troubleshoot issues, gain visibility into your workloads, and improve the health and performance of your apps.

In a test environment, deliberately create various non-ideal scenarios, such as deleting all worker nodes in a zone to replicate a zonal failure. Review the logs and metrics to check how your app recovers.

1. Test access: Test access to your app by creating a public or private NodePort on your worker nodes.
2. Understand logging and monitoring options: Choose solutions for app and cluster logging, audit logging, and monitoring based on your needs.
3. Monitoring through the console: Open the OpenShift web console to view information about your app resources.
4. Log Analysis and Monitoring: To monitor cluster health, forward logs to IBM Log Analysis and metrics to IBM Cloud Monitoring.

Update your app

Perform rolling updates and rollbacks of apps without downtime for your users.

1. Update strategy: Plan your strategy for keeping your app up-to-date.
2. Set up updates:
   • Add a rolling update to your deployment file
   • Set up a continuous delivery pipeline for a cluster.
3. Scaling: Enable horizontal pod autoscaling to automatically increase or decrease the number of instances of your apps based on CPU.

Secure your app

Use Kubernetes secrets to store confidential information, such as credentials or keys, and encrypt data in Kubernetes secrets to prevent unauthorized users from accessing sensitive app information.

1. Secrets: Store personal or sensitive information in Kubernetes secrets that your app can access.
2. Secret encryption: Set up a KMS provider and Encrypt secrets and verify encryption.

Expose your app

Publicly expose an app in your cluster to the internet or privately expose an app in your cluster to the private network only.

1. Plan service discovery:
   1. Understand the basics of Kubernetes service discovery.
   2. Choose an app exposure service that fits your requirements for incoming traffic to the app.
2. Expose your app:

   • Load balancers:

     • Classic clusters:
       1. Create an NLB 1.0 or NLB 2.0.
       2. Register a DNS subdomain for the NLB.
     • VPC clusters: Set up a VPC load balancer.

   • Ingress: Configure Ingress for the public network or the private network.

   • Routes: Create a route to expose your app on a subdomain.

Need help? Check out Troubleshooting Ingress and Troubleshooting load balancers.

Add app storage

1. Requirements: Determine your requirements for a storage solution.
2. Choose a solution: Using your storage requirements, choose a storage solution by comparing your options.

Need help? Check out the troubleshooting page for your persistent storage solution.

Add integrations

Enhance app capabilities by integrating various external services and catalog services in your cluster with your app.

1. Review supported integrations:

   • All supported integrations

   • Red Hat OpenShift on IBM Cloud partners

   • IBM Cloud services and third-party integrations

   • Cloud Paks

   • Operators

2. Add services to your cluster: Ask your cluster administrator to add the integration to your cluster.
3. Access services from your app: Ensure that your app can access the service. For example, to access an IBM Cloud service instance from your app, you must make the service credentials that are stored in the Kubernetes secret available to your app.

Need help? Check out Troubleshooting apps and integrations. {: tip}f