When adding Template Variables to a project and not checking "Use predefined values" it does not show up in the versions list nor in the dashboard. This happens when you enter a default value and also when you leave the field blank.

Components of a project mesh do not show the configuration templates of their project/project version.

Currently O-Neko supports multiple deployment URLs only if they are defined in one ingress. Apparently we don't support multiple URLs from multiple ingresses and we should change that.

When a project is deleted all deployments of that project should be stopped/deleted.

Currently the running deployments remain in the cluster and need to be manually deleted.

O-Neko currently has a number of Java-Model-Classes (Project, DockerRegistry, etc...), but they are all always mutable.
I'd propose to have a readable and a writable version of each.
Of course they should offer methods to convert to the other type.
Based upon this two things can be achived:

• Write a caching layer on model level
• Have a in-memory-repo implementations (handy for unit-tests and a spring-profile without actual DB)

Currently it is impossible to login with passwords using specific special characters because the form data is not correctly URL encoded.

This can be tested e.g. by using this as a password: djx+x2XeoZ98QvNjVQaCCYEVexGQCqfxND*jdjfVVo

AC:

• The login request parameters should be correctly encoded
• Other requests we initiate should also be checked for encoding errors

I just stumbled upon this:
Once a helm registry is added it can no longer be modified (at least when you try to modify username and password).

The browser-log reveals this answer:
Error while interacting with helm registry BASEURL/chartrepo/sophora (sophora): Error: repository name (sophora) already exists, please specify a different name

While adressing this issues: This might be a good chance to give docker registries a better icon than this weird cowboy hut.

We have an official Helm Chart hosted here: subshell/helm-charts

In this repo we should add installation instructions with that Helm chart.

When a template doesn ot have the metadata set properly, O-Neko stumbles into an NPE in KubernetesDeploymentManagerImpl#addLabelToMeta(ObjectMeta meta, String key, String value) if meta is null:

if (meta.getLabels() == null) {
...
}

This should not happen in the first place but the user should also at least get a useful error message in cases like these.

We use the ace editor without configuring it. That works well enough but as our backend requires the files to be indented by spaces we should enforce this in the editor, too.

When a select variable has a value it should show as selected in the editing view. Currently the select-value shows as empty. The values are correctly visible on the dashboard.

Buggy edit view:

Correct dashboard view:

Edit: Apparently sometimes it works, though whether it works depends on the version. I could not find obvious similarities between the working or broken versions though.

Currently it is not possible to change a user's password because the authentication property in the object is not modification aware and does not cause the user to be dirty. Thus, the repository does not update the user in the database.

We currently do not have a process to create versioned releases. Releases should follow semantic versioning with git-tags.

All docker images should be pushed to https://hub.docker.com/r/subshellgmbh/o-neko

I've observed that the DockerRegistryPolling might get stuck in a state where a job appears to be running even though it isn't. This should not be possible.

Add support for helm charts and remove the old way of editing kubernetes resources directly in O-Neko.
A project version should therefore only contain a values.yaml.

The activity log has a layout bug:
If you're scrolling through a readonably long log then it won't be visible intially.
If you then however scroll down it will somehow appear as if it was a mis-aligned part ot the log.: