This is a draft document that was built and uploaded automatically. It may document beta software and be incomplete or even incorrect. Use this document at your own risk.

Jump to contentJump to page navigation: previous page [access key p]/next page [access key n]
Deployment, Administration, and User Guides › Deploying SUSE Cloud Application Platform › Eirini
ContentsContents
Deployment, Administration, and User Guides
  1. About This Guide
  2. I Overview of SUSE Cloud Application Platform
    1. 1 About SUSE Cloud Application Platform
    2. 2 Other Kubernetes Systems
  3. II Deploying SUSE Cloud Application Platform
    1. 3 Deployment and Administration Notes
    2. 4 Deploying SUSE Cloud Application Platform on SUSE CaaS Platform
    3. 5 Deploying SUSE Cloud Application Platform on Microsoft Azure Kubernetes Service (AKS)
    4. 6 Deploying SUSE Cloud Application Platform on Amazon Elastic Kubernetes Service (EKS)
    5. 7 Deploying SUSE Cloud Application Platform on Google Kubernetes Engine (GKE)
    6. 8 Installing the Stratos Web Console
    7. 9 Eirini
    8. 10 Deploying SUSE Cloud Application Platform Using Terraform
    9. 11 Setting Up a Registry for an Air Gapped Environment
    10. 12 SUSE Private Registry
  4. III SUSE Cloud Application Platform Administration
    1. 13 Upgrading SUSE Cloud Application Platform
    2. 14 Configuration Changes
    3. 15 Creating Admin Users
    4. 16 Managing Passwords
    5. 17 Accessing the UAA User Interface
    6. 18 Container Memory Limits and Requests
    7. 19 Cloud Controller Database Secret Rotation
    8. 20 Rotating Automatically Generated Secrets
    9. 21 Backup and Restore
    10. 22 Service Brokers
    11. 23 App-AutoScaler
    12. 24 Integrating CredHub with SUSE Cloud Application Platform
    13. 25 Buildpacks
  5. IV SUSE Cloud Application Platform User Guide
    1. 26 Deploying and Managing Applications with the Cloud Foundry Client
  6. V Troubleshooting
    1. 27 Troubleshooting
  7. A Appendix
  8. B GNU Licenses
Navigation←→
Deployment, Administration, and User Guides › Deploying SUSE Cloud Application Platform › Eirini
Top
←→
Applies to SUSE Cloud Application Platform 2.1.1

9 Eirini

  • File Name: cap_depl_eirini.xml
  • ID: no ID found
9.1 Limitations and Other Considerations
9.2 Enabling Eirini

Eirini, an alternative to Diego, is a scheduler for the Cloud Foundry Application Runtime (CFAR) that runs Cloud Foundry user applications in Kubernetes. For details about Eirini, see https://www.cloudfoundry.org/project-eirini/ and http://eirini.cf

Different schedulers and stacks have different memory requirements for applications. Not every combination is tested so there is no universal memory setting for Cloud Application Platform, and because it depends on the application deployed, it is up to the user to adjust the setting based on their application.

9.1 Limitations and Other Considerations

  • File Name: cap_depl_eirini.xml
  • ID: sec-cap-eirini-considerations

When using Eirini, it is important to take into consideration:

  • If you are upgrading from SUSE Cloud Application Platform 2.0.1 to 2.1.0 and plan to convert from Diego to Eirini, please upgrade your Diego environment to SUSE Cloud Application Platform 2.1.0 first and then migrate to Eirini as the earlier CAP versions relied a technical preview version of Eirini.

    In this situation, your current applications relying on the cflinuxfs3 stack need to be converted to the sle15 stack. You can re-push your applications with cf push APP_NAME -s sle15 to do so, otherwise your applications will crash on Eirini.

  • Applications on Eirini will require slightly more memory than on Diego. From testing, add an additional 32 MB to your application's manifest. The increase may vary, depending on your application.

  • TCP routing is not available in Eirini deployments at this time.

  • Eirini requires the k8s-metrics-server to be installed on the Kubernetes environment where SUSE Cloud Application Platform is installed in order for Stratos Metrics to work.

  • Stratos Metrics will not show disk stats on Eirini.

  • When there is a Kubernetes outage, Eirini will not automatically restart applications upon its return. You will need to manually start them up at present.

9.2 Enabling Eirini

  • File Name: cap_depl_eirini.xml
  • ID: sec-cap-eirini-enable

  1. To enable Eirini, and disable Diego, add the following to your kubecf-config-values.yaml file. 

    features:
  eirini:
    enabled: true

    When Eirini is enabled, both features.suse_default_stack and features.suse_buildpacks must be enabled as well. A cflinuxfs3 Eirini image is currently not available, and the SUSE stack must be used. By default, both the SUSE stack and buildpacks are enabled.

    Note
    Note

    • After enabling Eirini, you will still see the diego-api pod. This is normal behavior because the Diego pod has a component required by Eirini.

    • Eirini will only work on a cluster that has the parameter --cluster-domain set to cluster.local.

  2. Deploy kubecf.

    Refer to the following for platform-specific instructions:

  3. In order for Eirini to report application metrics, Metrics Server (link xlink:href="https://github.com/kubernetes-sigs/metrics-server"/> must be installed.

    Note that --kubelet-insecure-tls is not recommended for production usage, but can be useful in test clusters with self-signed Kubelet serving certificates. For production, use --tls-private-key-file. 

    tux > helm install metrics-server stable/metrics-server --set args[0]="--kubelet-preferred-address-types=InternalIP" --set args[1]="--kubelet-insecure-tls"
→Chapter 10 Deploying SUSE Cloud Application Platform Using Terraform←Chapter 8 Installing the Stratos Web Console
Print this page

© 2022 SUSE