Introduction
Introduction
Introduction
Introduction
Introduction
Introduction
Introduction
Introduction
Introduction
Introduction
Introduction
Introduction
Introduction
Introduction
Introduction
Introduction
Introduction
Introduction
Introduction
Introduction
Introduction
Introduction
Introduction

Kubectl plugin release notes

2 minute readExtensibilityDeveloper productivity

1.7.1

  • In v1.7.0, for Run Custom Command, there was an issue with the order that commands were handled. In 1.7.1, this isssue has been fixed.

    NOTE: If you are currently using v1.7.0, it is suggested to update to v1.7.1 to avoid issues with handling certain `kubectl` commands for *Run Custom Command*.

1.7.0

  • To customize Kubernetes objects, support for Kustomize files has been added. Specifying a kustomization file is now possible when configuring application microservice deployments, and as a Specification source option for the Create Or Update Objects, Delete Objects, and Describe Objects procedures. To include a kustomization file in the Run Custom Command, use the Additional options for kubectl field with -k=<\path\to\directory>.

    TIP: To use a Kustomize file in application microservice deployments, select menu:Definition type[YAML] and *Enable Kustomization*. Follow the instructions in the parameter tool tips to supply the path for the file.

  • For application microservice deployments, fixed issue that occurred when the Definition source was a Git repository and a file path was specified in Relative path.

  • For application microservice deployments, fixed issue that occurred when the Definition source was YAML Content and a directory path was specified in the Path to YAML file/folder field.

  • Improved usability of Run Custom Command procedure.

  • IMPORTANT: For Run Custom Command, if you are using kubectl delete, it must be placed in the additionalOptionsForKubectlCommand field. If it is placed in a different field, you will receive a Error: flags cannot be placed before plugin name: message when the procedure runs.

1.6.0

  • Upgraded dependencies.

  • Migrated to Java 17 and Groovy 3.

    Because of the Java versions supported by CloudBees CD/RO, you can only use EC-Kubectl v1.6.0 with CloudBees CD/RO agents v10.11 and later.

1.5.0

  • Added support for handling inconclusive pauses in Argo Rollouts.

  • Fixed issue that caused failure when both Relative path and YAML content were specified.

1.4.1

  • Updated plugin to support multipart YAML files.

1.4.0

  • Added support for Argo Rollouts blue-green and canary deployments.

1.3.1

  • Updated the logger.

1.3.0

  • Added microservices support.

  • Ported the plugin to PDK.

1.1.4

  • The documentation has been migrated to the main documentation site.

1.1.3

  • Updated logger to slf4j.

1.1.2

  • Renaming to "CloudBees CD/RO".

1.1.1

  • Fixed Gateways compatibility in the Dependency Management procedure.

1.1.0

  • Provisioning of binary dependencies (for example, Grape jars) in the agent resource is now delivered through a new mechanism called Plugin Dependency Management. Now, binary dependencies are seamlessly delivered to the agent resource from the Flow Server when a new version of a plugin is invoked for the first time. The Flow Repository setup is no longer required for this plugin.

1.0.3

  • Fixed an issue with ec-groovy trying to fetch dependencies from Maven, instead of using the local cache.

1.0.2

  • Renamed Electric Cloud to CloudBees.

1.0.1

  • Configurations can now be created by users with an "@" sign in their name.

  • Fixed the display of the available configurations list within the Flow UI when configuring procedures.

1.0.0

  • First release.

Deploy microservices using the Kubectl plugin