Skip to content

Latest commit

 

History

History
78 lines (63 loc) · 2.8 KB

CONTRIBUTING.md

File metadata and controls

78 lines (63 loc) · 2.8 KB
Raw

Contributing

Overview

This documents explains the processes and practices recommended for contributing enhancements to the Kubernetes Dashboard charm.

  • Generally, before developing enhancements to this charm, you should consider opening an issue explaining your use case.
  • If you would like to chat with us about your use-cases or proposed implementation, you can reach us at Canonical Mattermost public channel or Discourse. The primary author of this charm is available on the Mattermost channel as @jnsgruk.
  • Familiarising yourself with the Charmed Operator Framework library will help you a lot when working on new features or bug fixes.
  • All enhancements require review before being merged. Code review typically examines
    • code quality
    • test coverage
    • user experience for Juju administrators this charm.
  • Please help us out in ensuring easy to review branches by rebasing your pull request branch onto the main branch. This also avoids merge commits and creates a linear Git commit history.

Developing

You can use the environments created by tox for development:

tox --notest -e unit
source .tox/unit/bin/activate

Testing

tox -e fmt           # update your code according to linting rules
tox -e lint          # code style
tox -e unit          # unit tests
tox -e integration   # integration tests
tox                  # runs 'lint' and 'unit' environments

Build charm

Build the charm in this git repository using:

charmcraft pack

Deploy

# Create a model
juju add-model dashboard
# Enable DEBUG logging
juju model-config logging-config="<root>=INFO;unit=DEBUG"
# Deploy the charm
juju deploy --trust ./kubernetes-dashboard_ubuntu-20.04-amd64.charm \
  --resource dashboard-image=kubernetesui/dashboard:v2.4.0 \
  --resource scraper-image=kubernetesui/metrics-scraper:v1.0.7

If, for some reason the charm fails to clean up the Kubernetes resources it creates, they can be removed as follows:

kubectl -n dashboard delete serviceaccount kubernetes-dashboard
kubectl -n dashboard delete svc kubernetes-dashboard
kubectl -n dashboard delete svc kubernetes-dashboard-metrics-scraper
kubectl -n dashboard delete secret kubernetes-dashboard-certs
kubectl -n dashboard delete secret kubernetes-dashboard-csrf
kubectl -n dashboard delete secret kubernetes-dashboard-key-holder
kubectl -n dashboard delete cm kubernetes-dashboard-settings
kubectl -n dashboard delete role kubernetes-dashboard
kubectl -n dashboard delete rolebinding kubernetes-dashboard
kubectl delete clusterrole kubernetes-dashboard
kubectl delete clusterrolebindings kubernetes-dashboard