Skip to content

Latest commit

 

History

History
266 lines (201 loc) · 11.3 KB

CHANGELOG.md

File metadata and controls

266 lines (201 loc) · 11.3 KB
Raw

3.6.0

Library updates

  • Update of all dependencies to the latest versions.
  • Min. GoLang Version is 1.22.5

3.5.0

Library updates

  • Update of all dependencies to the latest versions.
  • Min. GoLang Version is 1.20

3.4.0

Library updates

  • Update of all dependencies to the latest versions.

3.3.0

Bugfixes

  • Fixed issue with old deploy only nginx value files #48
  • Fixed issue with reduced project config files for Nginx deploy only. Now only the nginx and base config is still required. #47

Library Updates

  • Updated the base libraries to current versions

3.2.0

Configuration to keep temporary files

Now it is possible to set a configuration to keep the temporary files for the configuration deployments. The configuration can be set in the main or in the project configuration:

k8sManagement:
  # keep generated temporary files
  keepGeneratedTemplates: false

(see config/k8s_jcasc_mgmt.yaml)

To avoid to check those files in, please add the following line to your .gitignore

__k8smgmt__*

Bugfixes

There was a path error for the migration assistant, which should be fixed now.

3.1.0

Bugfixes

  • The uninstall was unable to load the configuration, which made it impossible to uninstall only namespaces for deployment.
  • In Jenkins there were changes in the charts regarding the mode and the label for the controller.

The jcasc_config.yaml files in the templates directory and in the project directories must start with this:

jenkins:
  systemMessage: "{{ .JCasc.SystemMessage }}"
  labelString: "{{ .JenkinsHelmValues.Controller.CustomJenkinsLabels }}"
  mode: "EXCLUSIVE"
  • labelString defines the old custom Jenkins label to allow the controller to execute the seed job.
  • mode was also set in the jenkins_helm_values.yaml, but is now also required in the JCasC configuration.

3.0.0

Introducing better template placeholder

The previous versions were still fully compatible with the deprecated bash version. With version 3.0.0 this compatibility is no longer given.

The new template system is based on Golang templates (https://golang.org/pkg/text/template/) and allows a more flexible use, as well as the usual template/placeholder syntax from the Kubernetes environment.

Migration

The migration is described under docs/migration/MigrateV2_to_V3.md.

Placeholder documentation

Furthermore, the new placeholders are fully documented in docs/TemplatePlaceholder.md and the further linked files.

Refactored Project Generation

The "Create Project" area has also been completely redesigned under the hood. It now relies on a complete project structure instead of individual variables and substructures and associated methods that operate on this structure.

This is also used for the placeholders and associated methods that work on this structure.

This change was urgently needed to add more features like configuration-based deployments (instead of creating the project-specific YAML files) or deploying the tool as a central instance in a Docker container.

New configuration file per project

Every project stores now the original configuration as k8s_jcasc_project_config.yaml. This allows to deploy applications directly from the configuration with the latest templates. The tool checks if there are some value files available. If this is not the case, it generates them temporary from the configuration and deletes them after a successful deployment.

The skippable files are:

  • jenkins_helm_values.yaml
  • nginx_ingress_helm_values.yaml
  • pvc_claim.yaml

New input field for additional Namespaces

Additional namespaces are now supported in the UI and the CLI version. Multiple namespaces can be added comma separated.

2.9.0 Small improvements and dependency updates

Dependency updates

This release updates the base libraries. Mainly fyne.io to 2.0.0.

Bugfixes

Fixed a minor bug where the GUI does not initially display the namespace dropdown.

Improvements

There is a new option to add a domain for the load balancers. Domains can be used in the templates with the placeholder "##JENKINS_URL##".

2.8.1

Bugfixes

This version fixes a bug in the resolution of the paths of the alternative secret files. Now the path for the alternative secrets is always the same as the path of the global secrets file.

Dependency updates

Update of the dependencies.

2.8.0

Bugfixes

This version fixes a problem with the namespace events after creating a new project.

External DNS annotations

This version introduces support for external DNS annotations on the Nginx load balancer service. To activate it, the following configurations can be changed in your project configuration:

# enable annotations on the load balancer service
NGINX_LOADBALANCER_ANNOTATIONS_ENABLED=false

# external DNS hostname
NGINX_LOADBALANCER_ANNOTATIONS_EXT_DNS_HOSTNAME="domain.tld"
# external DNS TTL time in seconds
NGINX_LOADBALANCER_ANNOTATIONS_EXT_DNS_TTL=60

These values are replacing the annotations block in the nginx_ingress_helm_values.yaml:

    annotations:
      enabled: ##NGINX_LOADBALANCER_ANNOTATIONS_ENABLED##
      external_dns_hostname: "##NAMESPACE##.##NGINX_LOADBALANCER_ANNOTATIONS_EXT_DNS_HOSTNAME##"
      external_dns_ttl: ##NGINX_LOADBALANCER_ANNOTATIONS_EXT_DNS_TTL##

The default for new DNS names is <namespace>.<ext_dns_host>. This version supports no direct UI edit (but it is possible to abuse e.g. the Jenkins Welcome Message).

Please update this file in the project templates, if modified templates are used.

If own charts are used, please update the following files in the nginx-ingress-controller folder:

2.7.0

This release mainly updates the underlying fyne.io framework to version 1.4.0. With this update the UI is much better and gets a fresher color scheme.

2.6.0

Introduction of multiple secret files

To set up multiple secret files, simply add new files in the same directory where the secrets.sh(.gpg) is located. These files need the prefix secrets_.

2.5.0

  • Fixes the error that after project creation the new namespace is not available and the application must be restarted.

2.4.0

  • Bugfix that Kubernetes Server certificate has not been replaced in the template
  • Adding support for multiple cluster certificates
    • The configuration KUBERNETES_SERVER_CERTIFICATE is now a fallback/default configuration.
    • With KUBERNETES_SERVER_CERTIFICATE_<context_name> it is now possible to add certificates for multiple contexts. The context name should not contain spaces!
    • Examples:
      • KUBERNETES_SERVER_CERTIFICATE_CLUSTER_A is for the context cluster_a
      • KUBERNETES_SERVER_CERTIFICATE_PRODUCTION-CLUSTER is for the context production-cluster

2.3.0

2.2.0

  • Update of libraries:
    • fyne: 1.3.2
      • fyne had some cache issues, which are solved with new version
    • crypto (latest branch)

2.1.0

  • Update of fyne to 1.3.1
  • Better support for server only environments
    • It is possible to use go run -tags cli k8s-jcasc-mgmt.go to avoid compile with fyne and its dependencies (gcc, x11,...)

2.0.1

Introducing new UI

  • K8S-Jcasc-Management supports now native UIs for the following platforms:
    • Windows
    • Linux and BSD
    • MacOS X

This was realized with the fyne framework.

To use K8S-JcasC-Management on a CLI, you can start it with the -cli flag.

Build hints

If you have trouble compiling the project, please visit the fyne developer site first to check the prerequisites. On Windows, it is recommended to install TDM-GCC - tdm-gcc.tdragon.net, which works very easily. It can be required to set the PATH variable to the TDM-GCC directory if the go compiler still wants a GCC.

Using on server-systems only (without GUI)

If you have trouble or if you want to use it on a server without X11, you can also exchange the !ignore and ignore in first-line comment at the /app/app_cli.go and /app/app_gui.go file. Golang will then use the app_cli.go file to compile and ignores the GUI implementation completely.

Screenshots

Welcome (Windows)

alt text

Deployment (Mac Dark Theme)

alt text

Create Project (Mac Light Theme)

alt text

1.13.1

  • Hotfix for the configuration of encrypted users.
    • Fixes the issue, that JENKINS_MASTER_ADMIN_PASSWORD_ENCRYPTED and JENKINS_MASTER_PROJECT_USER_PASSWORD_ENCRYPTED need encrypted password surrounded with ' characters, that the bash version will not interpret this configuration as arguments.

1.13.0

  • Support for create namespace from k8s-jcasc-mgmt
  • Default logging enabled.
    • k8s_jcasc_mgmt.cnf has now the following 3 parameters:
      • K8S_MGMT_LOGGING_LOGFILE: default is output.log. This defines the default logfile. This value can be overwritten with the -logfile argument or simply comment it to disable it.
      • K8S_MGMT_LOGGING_ENCODING: default is: console. Allows the default logging type (console or json)
      • K8S_MGMT_LOGGING_OVERWRITE_ON_START: default is: true. Defines if logfile should be re-created on start. In this case, the system moves the old log (if exists) to the defined logfile name with suffix .1. Example: output.log.1.

1.12.1

Features:

  • create new projects for Jenkins administration
  • manage secrets
    • encrypt/decrypt secrets for secure commit to a VCS (version control system)
    • apply secrets to Kubernetes
      • for each project while installation or as an update (applySecrets)
      • for all known namespaces, that are configured in the ip_config.cnf file (applySecretsToAll)
    • store secrets globally for easy administration
    • store secrets per project for more security
  • manage the Jenkins instances for a namespace with the project configuration
    • install
      • create namespace if it does not exist
      • install Jenkins
      • install nginx-ingress-controller per namespace (if configured)
      • install load balancer and ingress for Jenkins
    • uninstall
      • uninstall Jenkins installation
      • uninstall nginx-ingress-controller per namespace (if configured)
      • uninstall load balancer and ingress for Jenkins (other ingress routes will not be changed)
    • upgrade
  • internal log viewer
  • logging in JSON or console format

-> This release is equal to the 1.12.1 version of the bash implementation (https://github.com/Ragin-LundF/k8s-jcasc-management).