It’s been a busy week in the land of documentation. Clowder also received some new updates paving the way for full Cyndi support, along with some important technical debt cleanup. Read all the latest updates here.

Clowder

Production Updates#

Shared DB support has now landed in production, along with support for the private ports , which adds Clowder support for internal endpoints that are intended to be accessed via Turnpike on internal.cloud.redhat.com.

Documentation Updates#

New documentation for each Clowder provider has been added and is accessible via a Clowder-specific RTD site . The Clowder docs have also been added to the internal documentation page (pushed to stage, should be promoted to prod shortly).

A brand new How to Use guide has been created , which explains the basics of ClowdApps and ClowdEnvironments and how to set up a local dev environment using Clowder.

Strimzi Minikube deployment#

Since working with Cyndi will require a Strimzi deployment, a new Minikube installation script has been created along with initial support for Clowder to deploy KafkaConnect CRs.

Istio initial work#

Work has been ongoing to deploy the core platform into an Istio Service Mesh. mTLS has been confirmed to work for service-to-service calls, configured transparently to apps. Isolated OSD and AWS accounts for FedRAMP stage have been requested to be added to app-interface. Once these resources are in place, the service mesh operators and apps will start to be deployed to the new stage environment.

IQE support for cdappconfig.json#

An important MR has been merged into IQE to support loading service configuration from the config that Clowder generates. This will allow K8s Jobs/CronJobs to run IQE against a Clowder-enabled environment and receive the correct configuration for hostnames of services. This is how we expect to run IQE jobs in pr_check.sh once the change is released.

Frontend deployed to ephemeral environments

If you’re interested in deploying the frontend to an ephemeral environment, you can follow this guide to use Bonfire to get it set up. Be sure to follow the Bonfire getting started guide before trying to deploy the frontend.

Legacy Documentation

We’re moving away from using the old platform docs URL as a frontend to our documentation and instead have migrated over to internal.cloud.redhat.com . Though this will remain active for a short while longer, it is planned to be decommissioned soon. For this reason, we migrated all the content at the old location to live under ‘Legacy docs’ in the new location. This is in stage already and will be deployed to prod soon.