mario-f/cert-manager-selfservice

A service utilize cert-manager in kubernetes cluster to distribute certificates.

cert-manager-selfservice's Issues

Create a proper in program documentation

Create an automatic documention and overview how to use this cert-manager-selfservice instance starting at the default (/) endpoint.

Possible Tasks:

• Information over this instance (Cleanup Intervals, Managed Certificates, etc...)
• Examples how to issue and manage a Certificate
• ...

[example] get-certifcate.sh use curl and optinal basic auth

Add optional basic auth and move to curl because it can handle theis case better

Todo -> Issue #1

Added prometheus metrics -> see Todos in code

use a semantic-release

use a semantic-release process instead or with goreleaser

[build] readd armv7 support

cypress fail to install on docker buildx linux/arm/v7
fix problem and readd support for linux/arm/v7

Default response till certificate is issued

Added self signed cert option for 204 response

Todo -> Issue #6

Use 304 Not Modified (test with wget)

[helm] consider return chart from mario-f/helm-charts

Because the project is so tightly bond with the helm chart it can make more sense to host the helm chart in this repository as well.

This will also enable automatic versioning, testing and release in one step also include prereleases for both chart and applikation.

Cleanup optional or cooperative

Prevent cleanup of certificates that eventually used by other ressources:

• find a way to make it existing side-by-side

Provide service scripts

Provide a per domain endpoint with linux scripts predefined for donwload

Todo -> Issue #2

Adding more endpoints for different result types (status)

Profiles

Implement profiles matching domains for different configurations

Implement authentication

Implement a authentication function for admins and additional token based for each certificate

[security] pem should not yield private key

The pem text/plain result should not return the private key by default

k3s development suite

Try to create a full self contained development environment created on k3s (or other alternative if better)

[development] generator quickstart

add a working quickstart to use the generator

Split openapi.yaml in different files

To make usage of openapi definition more usable split it into seperat files and make sure all tools (incl. vscode preview) can handle this.

Localisation

Provide localisation in web frontend with i18n

Clientmode

Create a client handling certificate requests as service or cronbased

[test] integration test based on the development cluster

create an github action for integrations test against a matrix oh k3s/cert-manager versions

Proper integrade swagger-ui

fix the swagger-ui integration at /swagger just not has styles for now