Resolve "xta-test-server helm-chart mit Deployment und Keystore-Secrets/Certificate-Resources"

Closes #2 (closed)

changed milestone to %Dataport Sprint 13+14

added enhancement label

added 1 commit

• e455ecc7 - #2 (closed) OZG-7121 pom: Remove outdated documentation and add helm to pipeline

Compare with previous version

added 1 commit

• 8b81c98d - #2 (closed) OZG-7121 pipeline: Add helm unittest plugin

Compare with previous version

added 1 commit

• 802295a1 - #2 (closed) OZG-7121 pipeline: Add git to helm jobs

Compare with previous version

added 1 commit

• 846107f0 - #2 (closed) OZG-7121 pipeline: Post helm package to nexus

Compare with previous version

added 1 commit

• 0234f1bd - #2 (closed) OZG-7121 pipeline: Use semver

Compare with previous version

added 1 commit

• 90522aac - #2 (closed) OZG-7121 pipeline: Adjust helm unittest install

Compare with previous version

added 1 commit

• 9159b3f7 - #2 (closed) OZG-7121 pipeline: Use references for helm

Compare with previous version

added 1 commit

• 6eb928ab - #2 (closed) OZG-7121 pipeline: Adjust references for helm

Compare with previous version

added 1 commit

• c1e491a1 - #2 (closed) OZG-7121 pipeline: Unify test-helm

Compare with previous version

added 1 commit

• ed472681 - #2 (closed) OZG-7121 pipeline: Adjust helm-chart version

Compare with previous version

Die üblichen docker tags mit master-1.2.3 und release-1.2.3 sind keine echten semantischen Versions-nummern. (hingegen wären 1.2.3-master und 1.2.3-release korrekt)

Helm erfordert echte semantische Versionsnummer, daher, denke ich, macht es Sinn, auch einheitlich für die DockerImages diese Versionen zu verwenden.

Das bricht dann allerdings mit dem Namensschema, das mgm bisher angewendet hat.

Wenn wir die Änderung für sinnvoll erachten, können wir das doch an mgm weitergeben. Ich sehe nicht, das dadruch etwas kaputt geht.

abgesehen von den Aspekten von Jan die ich so unterstütze finde ich die Lesbarkeit etwas besser bei "release-2.1.5"

Ich würde an der Stelle Vorschlagen mal noch Stefan zu fragen der muss im Zweiffelsfall mit unterschiedlichen Konventionen zurecht kommen bzw. Unterschiedliche Konventionen durch die Pipelines durch bekommen ob es da zu Problemen kommen kann

added 3 commits

• cba17192 - #2 (closed) OZG-7121 Remove asciidoc Readme
• 23f8977f - #2 (closed) OZG-7121 pipeline: Add more docker tags
• e9882ee5 - #2 (closed) OZG-7121 pipeline: Package jar instead of just compile

Compare with previous version

added 1 commit

• 1d07b1a8 - #2 (closed) OZG-7121 pipeline: Use hyphen instead of plus

Compare with previous version

added 1 commit

• efc8aa07 - #2 (closed) OZG-7121 helm: Use namespace-ca-issuer

Compare with previous version

added 1 commit

• e81401fa - #2 (closed) OZG-7121 helm: Configure keystore and truststore in deployment

Compare with previous version

added 1 commit

• 5ea265ff - #2 (closed) OZG-7121 helm: Configure ingress with same secret as in cluster

Compare with previous version

added 1 commit

• ad4c8b1f - #2 (closed) OZG-7121 helm: Use letsencrypt for ingress

Compare with previous version

added 1 commit

• 637fa55e - #2 (closed) OZG-7121 helm: Resolve helm install warnings

Compare with previous version