Giter VIP home page Giter VIP logo

console-charts's Introduction

Archived 2023-09-12

See lightbend/akka-meta #245

CircleCI

console-charts

Contains public Helm charts related to the Lightbend Console. Lightbend's helm repo is available at https://repo.lightbend.com/helm-charts.

Project layout

All projects must conform to the Helm chart layout.

If there are files that you don't want included in the chart, add them to a .helmignore file in your project directory.

Project Makefile

All projects must have a Makefile that implements the targets:

  • lint: Should do preliminary checks to confirm the project is ready for packaging.
  • package: Should create the chart tarball and push it up to the console-charts/docs directory.
  • test: Typically run by Travis to test the release.

A default common.mk file is included that can be used for this purpose, although a project is free to implement these targets as they see fit.

console-charts Makefile

The default target of the top-level Makefile packages all the charts and then builds the index.yaml file based on the tarballs.

If any of the lint, package, or test targets are invoked, they are recursively invoked on each of the projects. To run over a particular subset of projects just define a value on the command line. e.g. make package CHARTS=sample-project

Helm install a project:

To install the Helm chart for a particular project...

kubectl create serviceaccount --namespace kube-system tiller

kubectl create clusterrolebinding tiller-cluster-admin --clusterrole=cluster-admin --serviceaccount=kube-system:tiller

helm init --service-account tiller

helm repo add lightbend-helm-charts https://repo.lightbend.com/helm-charts

helm repo update

helm install lightbend-helm-charts/<chart-name> --name=<release-name> --namespace=lightbend --debug

Upgrade

helm repo update
helm upgrade lightbend-helm-charts/<chart-name> --name=<release-name> --namespace=lightbend --debug

Cutting a Release / Publishing Charts

See the Google doc for releasing Enterprise Suite Console for the definitive process.

Availability

Published Lightbend helm charts are available from the the public helm repo. Assuming you have es-repo mapped to the https://repo.lightbend.com/helm-charts repo in helm, then for a list of all currently published Lightbend charts run:

helm repo update
helm search es-repo

Maintenance

Enterprise Suite Team [email protected]

License

Copyright (C) 2018 Lightbend Inc. (https://www.lightbend.com).

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this project except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0.

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

console-charts's People

Contributors

alanngai avatar andreatp avatar craigupson avatar dbrinegar avatar ennru avatar jedahu avatar jsravn avatar justinpihony avatar katsutoxin avatar longshorej avatar marcoderama avatar mitkus avatar pcraddick avatar seglo avatar srikanthops avatar typesafe-tools avatar yuchaoran2011 avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

console-charts's Issues

Repository rename broke URL references

While we have been trying to update old references to https://lightbend.github.io/helm-charts, some still remain (including some on third-party web sites that are out of our control). If we can avoid breaking this URL, it would be better.

Renaming this repository from helm-charts to console-charts seems to have broken the old URL, as GitHub pages isn't redirecting automatically from https://lightbend.github.io/helm-charts/index.yaml to https://lightbend.github.io/console-charts/index.yaml

Upgrade ubuntu image version used in CircleCI

Got this email from Circle today. We need to upgrade the ubuntu image version used in our circle config:


Hello,

We are deprecating Ubuntu 16.04-based machine images on CircleCI in preparation for an EOL on Tuesday, May 31, 2022 to ensure your builds remain secure. For a detailed overview of how this will affect your workflow, read the blog article here.

We will also be conducting temporary brownouts on Tuesday, March 29, 2022, and again on Tuesday, April 26, 2022 during which these images will be unavailable.

We are contacting you because one or more of your projects has a job that uses an Ubuntu 16.04-based image.

The project(s) using an image based on Ubuntu 16.04 are:

[console-charts]

If you have specified an Ubuntu 16.04-based image please see our migration guide to upgrade to a newer version of Ubuntu image in order to avoid any service disruption during the brownout & subsequent EOL.

We will also be releasing a CircleCI Ubuntu 22.04 image on April 22nd offering the flexibility to upgrade to the latest LTS version of Ubuntu image before we remove older versions permanently. A beta version of the image will be available March 21st.

Our team is committed to getting you the most performant builds while maintaining security.

apiVersion value changes between hard coded and using Values.yaml references

The value of "apiVersion" in each of the deployments changes between being hard coded as, "extensions/v1beta1" and using a reference to the same value in Values.yaml (see the difference between alertmanager-deployment.yaml and es-console-deployment.yaml as examples of this). Should these all be consistent across all deployment.yaml files?

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.