Giter VIP home page Giter VIP logo

galaxy's Introduction





Multi-cluster Configuration Management for Edge, Multi-Cloud, and Hybrid Cloud

    Join Slack

KubeStellar is a Cloud Native Computing Foundation (CNCF) Sandbox project that simplifies the deployment and configuration of applications across multiple Kubernetes clusters. It provides a seamless experience akin to using a single cluster, and it integrates with the tools you're already familiar with, eliminating the need to modify existing resources.

KubeStellar is particularly beneficial if you're currently deploying in a single cluster and are looking to expand to multiple clusters, or if you're already using multiple clusters and are seeking a more streamlined developer experience.

KubeStellar High Level View

The use of multiple clusters offers several advantages, including:

  • Separation of environments (e.g., development, testing, staging)
  • Isolation of groups, teams, or departments
  • Compliance with enterprise security or data governance requirements
  • Enhanced resiliency, including across different clouds
  • Improved resource availability
  • Access to heterogeneous resources
  • Capability to run applications on the edge, including in disconnected environments

In a single-cluster setup, developers typically access the cluster and deploy Kubernetes objects directly. Without KubeStellar, multiple clusters are usually deployed and configured individually, which can be time-consuming and complex.

KubeStellar simplifies this process by allowing developers to define a binding policy between clusters and Kubernetes objects. It then uses your regular single-cluster tooling to deploy and configure each cluster based on these binding policies, making multi-cluster operations as straightforward as managing a single cluster. This approach enhances productivity and efficiency, making KubeStellar a valuable tool in a multi-cluster Kubernetes environment.

Website

See kubestellar.io.

Contributing

We ❤️ our contributors! If you're interested in helping us out, please head over to our Contributing guide and be sure to look at main or the release of interest to you.

This community has a Code of Conduct. Please make sure to follow it.

Getting in touch

There are several ways to communicate with us:

Instantly get access to our documents and meeting invites at http://kubestellar.io/joinus

❤️ Contributors

Thanks go to these wonderful people:


Jun Duan

👀

Braulio Dumba

👀

Mike Spreitzer

👀

Paolo Dettori

👀

Andy Anderson

👀

Franco Stellari

👀

Ezra Silvera

👀

Bob Filepp

👀

Effi Ofer

👀

Maria Camila Ruiz Cardenas

👀

Andrey Odarenko

👀

Aashni Manroa

👀

Kevin Roche

👀

Nick Masluk

👀

Francois Abel

👀

Nir Rozenbaum

👀

Maroon Ayoub

👀

Graham White

👀


FOSSA Status

Cloud Native Computing Foundation Logo
We are a Cloud Native Computing Foundation sandbox project.
Kubernetes and the Kubernetes logo are registered trademarks of The Linux Foundation® (TLF).
© 2022-2024. The KubeStellar Authors.

galaxy's People

Contributors

cwiklik avatar dependabot[bot] avatar pdettori avatar seepgoel avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

galaxy's Issues

feature: add support for Loki in OpenShift to shadow-pod controller

Feature Description

Loki-logger pod now expects some new env variables when running in OpenShift:

  • LOKI_INSTALL_TYPE - this must be dev or openshift
  • TLS_CERT_FILE - must be specified for openshift
  • TLS_KEY_FILE - must be specified for openshift
  • LOG_TYPE - must be specified for openshift and can be application, infrastructur or audit - defaults to application if not specified

TLS_CERT_FILE and TLS_KEY_FILE can be get from the secret "logging-loki-querier-http" in the "openshift-logging" namespace on the openshift cluster where the loki instance has been installed.

Proposed Solution

1.. Update the install script to copy the secret "logging-loki-querier-http" from the "openshift-logging" namespace to the kubeflow namespace in the core cluster
2. Shadow pod controller gets also the env variable LOKI_INSTALL_TYPE, and configure the pod template for the Loki logger to pass the LOKI_INSTALL_TYPE flag.
3. if LOKI_INSTALL_TYPE ==openshift, it configures the pod template to get the certs from the secret "logging-loki-querier-http" in the kubeflow namespace

Want to contribute?

  • I would like to work on this issue.

Additional Context

No response

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.