Release Notes
The maintenance period for version v1.14.z (LTS) is from Sep 7, 2026 to Sep 7, 2027.
TOC
Compatibility and support matrixv1.15.0Features and EnhancementsFixed IssuesBreaking Changesv1.14.0Features and EnhancementsBreaking Changesv1.12.0Features and EnhancementsFixed IssuesKnown Issuesv1.10.1Features and EnhancementsFixed IssuesKnown Issuesv1.10.0 (LTS)Features and EnhancementsBreaking ChangesFixed IssuesKnown Issuesv1.9.0Features and EnhancementsBreaking ChangesFixed IssuesKnown Issuesv1.8.0Features and EnhancementsBreaking ChangesFixed IssuesKnown Issuesv1.7.0Features and EnhancementsBreaking ChangesFixed IssuesKnown Issuesv1.6.2Features and EnhancementsFixed IssuesKnown Issuesv1.6.0 (LTS)Features and EnhancementsBreaking ChangesFixed IssuesKnown IssuesCompatibility and support matrix
The following table shows the compatibility and support matrix between the Alauda Container Platform Connectors operator and ACP versions.
v1.15.0
Released on October 31, 2026.
Features and Enhancements
-
Pipeline Integrations can combine Connectors of different types. When a ResourceInterface sets
multipleMergeConnectors.allowCrossTypeConnectors: true, the extra Connectors of an Integration can come from other ConnectorClasses: for example, an OCI, Harbor or JFrog image Integration can also use a Maven Connector, and a Maven Integration can also use a Harbor Connector. In the workspaces that use the selected Connectors (selectedConnectors()), the required configuration files of every selected Connector are merged. The new schema-version 3 ResourceInterfacesociartifact-v2,harborociartifact-v3,jfrogociartifact-v2andmavenrepository-v2enable it; the earlier ResourceInterfaces stay installed for older frontends. Requires theenable-multi-connectorfeature flag and Tekton operator v4.14.0 or later. The schema-version 3 ResourceInterfaces are installed by default; on clusters with an older Tekton release, set thepipeline-integrationinstall flag to"<=2"to skip them. See Multiple Connectors and Install Flags. -
A new
jfrog-connector-automatic-creationTekton Task reconciles JFrog Artifactory repositories, a scoped identity and its permissions, then writes the JFrog Connector, its auth Secret, and per-namespace image pull Secrets into Kubernetes. Requires Artifactory Pro or higher. See JFrog Connector Automatic Creation Tekton Task to install it, Automatically Create and Reconcile JFrog Connector Resources with Tekton to use it, and Automatically Provision JFrog Resources When a Project Is Created to run it from a namespace event. -
Added a guide to enabling Connectors Proxy permissions and approval, with recommended settings for the Connectors Proxy and the CSI Driver. See Enable Proxy Permission Checks and Approval Gating and Recommended Settings.
-
Documented how often automatically created credentials are rotated and how the CSI
token.expirationsetting relates to it. See Credential rotation. -
The operator is now named Alauda Container Platform Connectors.
-
The operator bundle image is now published for both
amd64andarm64.
Fixed Issues
-
Resources installed by the operator are repaired again when they are changed or deleted in the cluster. Previously such drift was only corrected when the component spec changed or the operator pods restarted.
- The resources of every component are now also re-applied periodically: by default every 10 to 12 minutes (a 10-minute period plus up to 20% jitter). The period is set with the
INSTALLMANIFEST_RESYNC_PERIODenvironment variable, and0turns it off. - This fixes new ResourceInterface fields (such as
allowCrossTypeConnectors) staying missing after an in-place upgrade, when an extension applied its ResourceInterfaces before the core CRD was updated. - Also fixed in v1.14.z.
- The resources of every component are now also re-applied periodically: by default every 10 to 12 minutes (a 10-minute period plus up to 20% jitter). The period is set with the
-
The
gitlab-connector-automatic-creationTask now sendsexpires_atwhen it rotates a Group Access Token, so the rotated token keeps the configured lifetime instead of GitLab's one-week default. Rotating with a custom lifetime requires GitLab 16.6 or later; on older versions the Task logs a warning. If the requested lifetime exceeds the instance's maximum token lifetime, rotation now fails instead of silently issuing a one-week token. See Automatically Create and Reconcile GitLab Connector Resources with Tekton. Also fixed in v1.14.z. -
Searching the GitLab repository selector of a Pipeline Integration by group or
group/projectpath now returns matching projects. Previously only project names matched. Also fixed in v1.14.z. -
Updated the operator runtime base image, the Go toolchain (1.26.9) and Go dependencies to address known security vulnerabilities, including CVE-2026-78669 and CVE-2026-84445.
-
Rebuilt the
kubectlandglabtool images used by the automatic-creation Tasks on updated Alpine base images, addressing vulnerabilities in curl (CVE-2026-92392 and CVE-2026-92388) and other base packages. -
Automatic Connector creation: the namespace event adapter image is now referenced by tag only, so it is included in the offline package for air-gapped installations.
-
The
harbor-connector-automatic-creationTask image now takeskubectlfrom the connector-family image instead of the Alpine package, which carried vulnerabilities that image scanners did not report. -
Hardened the operator deployment: the bundle image runs as a non-root user, and the webhook and RBAC manifests were corrected to resolve Kubernetes static-analysis findings.
-
Moved the core component base image to Debian 13 and updated
golang.org/x/netto v0.62.0 to address known security vulnerabilities.
Breaking Changes
- Manual changes to resources installed by the operator are now reverted: immediately when the change is detected, and at the latest on the next periodic re-apply. Previously such changes persisted until the component spec changed or the operator restarted. To keep a manual change, add the
skip-sync: "true"annotation to that resource; the operator then stops updating it, including during upgrades. A deleted resource is still recreated.
v1.14.0
Released on September 7, 2026.
Features and Enhancements
-
JFrog Connector now supports pulling and pushing Docker images to JFrog Artifactory Docker Local repositories via a forward proxy, without embedding credentials in Pod or TaskRun specifications. The proxy CA certificate is mounted by the Connectors CSI Driver and can be trusted via the system trust store or
SSL_CERT_FILE. See Building Images Using JFrog Connector Forward Proxy in Kubernetes and Using JFrog Connector Forward Proxy in Tekton Pipeline. -
Added a manual-install guide for the standalone
connectors-autocreatecomponent while its manifest is not yet bundled by the connectors-operator. The guide explains the required admin Connectors and automatic-creation Tasks, how to apply the overlay, and how to trigger reconciliation for project namespaces. See Automatically Create Connectors for a Project. -
JFrog raw repository Pipeline Integrations can select a Local Generic repository, recursively load its files, and locally filter the complete list by repository-relative path. Downloads can select an existing file, while compatible upload Tasks can optionally consume a destination path. See JFrog Connector.
-
Nexus raw repository Pipeline Integrations can list and search files in a selected hosted raw repository, then provide the complete repository-relative path to download Tasks. Existing repository-only Integrations remain compatible. See Upload and Download Artifacts in a Nexus Raw Repository.
-
AccessPolicycheck rules acceptparams, letting a policy require that specific people or groups approve before access is granted. The built-inconnectors-approvals-in-pipelinerule readsapproversandnumberOfApprovalsRequired; whenapproversis absent the previous behavior is unchanged. See Restricting Who Can Approve.
Breaking Changes
-
The input passed to a check rule's
state.regoscript changed from the check resource itself to{ "object": <the check resource>, "check": <the check rule> }.This only affects you if both apply: the
enable-connectors-approvalfeature flag is on, and you wrote your own check-state Rego script. The built-in rules ship already migrated, so the default configuration is unaffected.In a custom script, read the resource through
input.objectinstead of reading it at the top level — for exampleinput.data.resultbecomesinput.object.data.result, andinput.status/input.metadatabecomeinput.object.status/input.object.metadata. The check rule and its params are available asinput.check.
v1.12.0
Features and Enhancements
- Added the
enable-pod-image-pull-via-connectorfeature flag (default off) to gate the OCI/Harbor PodWebhook's auto-rewrite of Pod container image addresses to the Connector Proxy URL. See Feature Flags. - Added the
enable-connector-apis-write-passthroughfeature flag (default off) to enable write methods (POST/PUT/DELETE/PATCH) on the Connectors API gateway. Authorization for enabled writes follows the same fine-grained SAR chain used forGET, controlled byenable-connector-apis-permissions. See Feature Flags and Write methods (passthrough). - Added Connector Generation, allowing aggregator Connectors such as Nexus or JFrog to materialize per-ecosystem child Connectors from
spec.generators. See Connector Generation. - Package the Connectors UI as a Console service-backend plugin managed by the operator.
- Added a guide for migrating Alauda DevOps v3 Integration and ClusterIntegration resources to Connectors using the
int2connCLI. See Migrating v3 Integrations to Connectors.
ConnectorsConfig Management
- Introduced
ConnectorsConfig— a cluster-singleton CR that manages all connector components from a single spec, replacing the need to manage individual component CRs (ConnectorsCore, ConnectorsGit, ConnectorsHarbor, etc.) directly. The operator auto-creates aConnectorsConfigon startup and automatically adopts any existing standalone component CRs. Configure the shared registry, labels, annotations, and feature flags once for all components, with per-component overrides where needed. See Installation. - Added
spec.installFlagstoConnectorsConfigto control installation behavior for specific cluster configurations. Thepipeline-integrationflag allows administrators to cap which ResourceInterface schema versions are deployed on clusters running legacy Tekton releases. See Install Flags and Feature Maturity.
SonarQube Connector Enhancements
- Provide the
sonarqube-connector-automatic-creationTekton Task to automate SonarQube project creation and connector initialization for Alauda Container Platform tenants and namespaces. Supports SonarQube 8.9.2 LTS and 25.1 LTA. More details:
GitLab Connector Enhancements
- Provide the
gitlab-connector-automatic-creationTekton Task to automate GitLab Personal Access Token initialization, rotation, and credential refresh for Alauda Container Platform tenants and namespaces. More details:
Nexus Connector Enhancements
- Provide the
nexus-connector-automatic-creationTekton Task to automate Nexus connector initialization and credential refresh for Alauda Container Platform tenants and namespaces. More details:- It can create or reconcile Nexus repositories (hosted, proxy, group), scoped user + role + per-repository privileges, the Connector authentication Secret, and the Nexus Connector resource, with rerun-based self-healing for partial failures.
- Automatically Create and Reconcile Nexus Connector Resources with Tekton
CSI Driver Enhancements
- The CSI Driver built-in configuration now includes a
.curlrcfile that workloads can pass tocurl --configto configure proxy and TLS settings without exporting environment variables. When using an HTTPS destination behind a TLS-intercepting forward proxy, pass--cacert /{mount-path}/ca.crtalongside--configto satisfy certificate verification. See Built-in Configurations.
Git Connector Enhancements
- Git and GitLab ConnectorClasses now scope the proxy
Authorizationheader to the proxy address ([http "<proxyAddress>"]) in the rendered.gitconfig, so the credential is not sent to other hosts such as submodule servers on a different Git instance. See Git ConnectorClass.
Harbor Connector Enhancements
- The
harborCliImageparameter of theharbor-connector-automatic-creationtask now has a built-in default and can be omitted in most deployments. - The
permissionsparameter now supports a multi-resource format (<resource1>:<verbs>;<resource2>:<verbs>), allowing a single entry to grant access to multiple Harbor resource types for the same project. The existing single-resource format remains fully supported. See Using Harbor Connector Automatic Creation Task.
Security updates
- The operator pod now uses an explicit projected ServiceAccount token volume and sets
automountServiceAccountToken: false, resolving Kubescape control C-0190. - Updated base images and resolved security vulnerabilities in OpenSSL (CVE-2026-45447 and related CVEs).
- Updated Go toolchain to 1.26.4, resolving GO-2026-5039 (net/textproto), GO-2026-5038 (mime), and GO-2026-5037 (crypto/x509).
Fixed Issues
- Before this update, when cloning a repository with submodules hosted on a different git server through a git-family Connector (git/gitlab/github), the submodule clone fails with 401/403 because the Connector proxy authentication header is sent globally to all servers. With this update, the authentication header is scoped to the proxy address only, so submodules from other git servers clone successfully, while submodules on the same Connector server remain unaffected.
- Before this update, when the custom CA certificate feature is enabled, Harbor Connector proxy client silently bypasses TLS verification, allowing connections with wrong CA certificates to succeed. With this update, when the custom CA certificate feature is enabled, Harbor Connector correctly performs TLS verification, rejecting connections with wrong CA certificates and accepting connections with correct CA certificates.
- Before this update, when using SonarQube Connector to run code scanning against SonarQube 8.9/9.9 servers, the scan fails with "You are not authorized to run analysis" due to incompatible authentication method. With this update, SonarQube Connector automatically adapts authentication to the server version, using Basic token auth on older versions and preferring Bearer token on newer versions, so scanning completes successfully.
- Before this update, the Connector forward proxy MITM-intercepted every HTTPS CONNECT request. As a result, in Tekton buildah task Containerfile RUN steps, requests to non-connector destinations such as curl, apt-get, and wget were also routed through the MITM proxy, forcing clients to trust the proxy CA even when the traffic did not need Connector interception. This caused major friction for buildah-based builds. With this update, the forward proxy chooses behavior based on whether the target matches a connector address: requests to connector addresses continue to use MITM with auth injection, while requests to non-connector addresses fall back to a transparent tunnel so the client sees the real upstream certificate and no proxy CA trust is required. This preserves proxy behavior for connector traffic while avoiding the incorrect CA requirement for unrelated HTTPS requests.
Known Issues
No issues in this release.
v1.10.1
Features and Enhancements
- Security updates: Updated base images, dependencies, and resolved security vulnerabilities.
Fixed Issues
- Before this update, the Connector forward proxy MITM-intercepted every HTTPS CONNECT request. As a result, in Tekton buildah task Containerfile RUN steps, requests to non-connector destinations such as curl, apt-get, and wget were also routed through the MITM proxy, forcing clients to trust the proxy CA even when the traffic did not need Connector interception. This caused major friction for buildah-based builds. With this update, the forward proxy chooses behavior based on whether the target matches a connector address: requests to connector addresses continue to use MITM with auth injection, while requests to non-connector addresses fall back to a transparent tunnel so the client sees the real upstream certificate and no proxy CA trust is required. This preserves proxy behavior for connector traffic while avoiding the incorrect CA requirement for unrelated HTTPS requests.
Known Issues
No issues in this release.
v1.10.0 (LTS)
Features and Enhancements
New Connectors
- Support integration with GitHub by using GitHub Connector. More details:
- Support integration with JFrog Artifactory by using JFrog Connector. More details:
- Support integration with Nexus Repository by using Nexus Connector. More details:
Permission and Access Control
- Added an additional
connectors/apispermission validation for Connector API access.- When
enable-connector-apis-permissionsis enabled, the system performs an additionalconnectors/apispermission check for Connectors API requests that browse tool data. This change separates Connector discovery from actual Connector API usage. - For more details, see Connectors Permission Model and Connector API.
- When
- Added an additional
connectors/proxypermission validation for Connectors Proxy access.- When
enable-connector-proxy-permissionsis enabled, the system performs an additionalconnectors/proxypermission check before workloads or CLIs use proxy-based Connector access. This change separates Connector discovery from actual runtime use. - For more details, see Connectors Permission Model and Connectors Proxy.
- When
- Added approval-gated access control for protected Connectors Proxy usage.
- When
enable-connectors-approvalis enabled together withenable-connector-proxy-permissions, administrators can useAccessPolicyandAccessRequestto require approval before a workload is allowed to use protected Connector proxy access. - For more details, see Connectors Approval & Permission Gating.
- When
- Added ACP platform roles for
AccessPolicyandAccessRequestresources, so approval resources follow the expected platform, project, and namespace permission model.
Feature Flag Management
- Support declarative feature flag configuration through the
ConnectorsCoreCRspec.featureFlagsfield. CR values override manifest defaults during reconciliation, eliminating the need to manually edit theconnectors-configConfigMap. For more details, see Feature Flags.
Harbor Connector Enhancements
- Support mounting
harbor-cli-configfrom Harbor Connector so workloads can useharbor-clithrough the connector proxy without exposing the original Harbor credential. More details: - Provide the
harbor-connector-automatic-creationTekton Task to automate Harbor connector initialization and credential refresh for Alauda Container Platform tenants and namespaces. More details:- It can create or reconcile Harbor projects, robot accounts, Connector Secrets, Harbor Connectors, and target namespace
imagePullSecrets. - Automatically Create and Reconcile Harbor Connector Resources with Tekton
- It can create or reconcile Harbor projects, robot accounts, Connector Secrets, Harbor Connectors, and target namespace
Custom CA Certificates
- Support custom CA certificates for Connectors that target tools served by an internal or private Certificate Authority (CA), preserving TLS verification instead of disabling it. When the
enable-custom-ca-certsfeature flag is enabled, administrators can register cluster-wide CA bundles via labeled Secrets in the system namespace and Connector authors can additionally provide a per-Connector CA viaspec.caCertSecretRef. The resulting trust pool is additive (system + global + per-connector) and load status is surfaced through the informationalCACertReadycondition. More details:
Other Enhancements
- Add
ca.crtto the Connectors-CSI built-in configuration as a replacement forca.cert. - When CSI approval is rejected, the driver now mounts a
.error.jsonfile (google.rpc.Status JSON) instead of blocking the Pod, allowing the workload to fail promptly. For more details, see Connectors Approval.
Deprecation Notice
ca.certwill be deprecated soon in the Connectors-CSI built-in configuration. Please useca.crtinstead. For more details, see: Connectors CSI Built-In Configurations
Security updates
Updated base images, dependencies, and resolved security vulnerabilities
Breaking Changes
- The Maven ResourceInterface has been renamed from
MavenArtifacttoMavenRepository. ThegroupId,artifactId, andversionparameters have been removed; the ResourceInterface now exposes a singlerepositoryattribute derived from the Connector address. Existing pipelines that reference the oldMavenArtifactResourceInterface or its removed parameters need to be updated.
Fixed Issues
- Before this update, when Connector accessed GitLab through the forward proxy, requests could carry X-Forwarded and related headers injected by an ALB or gateway. GitLab could return 403 even when the credentials were valid, causing page access or data retrieval to fail. With this update, Connector removes those gateway forwarding headers before forwarding requests, so GitLab access and data retrieval work normally when the credentials are valid.
- Before this update, when users configured an HTTPS Nexus Maven repository with a custom CA certificate in Connector, the Maven authentication check did not use the Connector's CA certificate and could fail certificate validation. With this update, Maven authentication checks use the CA certificate configured on the Connector, so users can complete authentication for HTTPS Nexus Maven repositories normally.
Known Issues
- Before this update, the Connector forward proxy MITM-intercepted every HTTPS CONNECT request. As a result, in Tekton buildah task Containerfile RUN steps, requests to non-connector destinations such as curl, apt-get, and wget were also routed through the MITM proxy, forcing clients to trust the proxy CA even when the traffic did not need Connector interception. This caused major friction for buildah-based builds. With this update, the forward proxy chooses behavior based on whether the target matches a connector address: requests to connector addresses continue to use MITM with auth injection, while requests to non-connector addresses fall back to a transparent tunnel so the client sees the real upstream certificate and no proxy CA trust is required. This preserves proxy behavior for connector traffic while avoiding the incorrect CA requirement for unrelated HTTPS requests.
- Before this update, the Connector forward proxy MITM-intercepted every HTTPS CONNECT request. As a result, in Tekton buildah task Containerfile RUN steps, requests to non-connector destinations such as curl, apt-get, and wget were also routed through the MITM proxy, forcing clients to trust the proxy CA even when the traffic did not need Connector interception. This caused major friction for buildah-based builds. With this update, the forward proxy chooses behavior based on whether the target matches a connector address: requests to connector addresses continue to use MITM with auth injection, while requests to non-connector addresses fall back to a transparent tunnel so the client sees the real upstream certificate and no proxy CA trust is required. This preserves proxy behavior for connector traffic while avoiding the incorrect CA requirement for unrelated HTTPS requests.
v1.9.0
Features and Enhancements
- Support Multiple Connectors in Connectors CSI Driver.
- Support permission control for Connectors Proxy capabilities via AccessPolicy.
- Security updates: Updated base images, dependencies, and resolved security vulnerabilities
Breaking Changes
Fixed Issues
No issues in this release.
Known Issues
No issues in this release.
v1.8.0
Features and Enhancements
- Connectors Core Capabilities and existing connectors (Git, OCI, Maven, PyPI, NPM, Kubernetes) have been promoted to Beta maturity level. For more details, see Feature Maturity.
- Add performance description and tuning guide to the documentation. For more details, see Performance Guide.
Deprecation Notice
- Added
registry-configconfiguration to OCI and Harbor ConnectorClasses. The legacydocker-config(oci)andconfig(harbor)configuration is now deprecated but remains functional for backward compatibility. It will be removed in a future release. When mounting Connector configurations, useregistry-configinstead ofdocker-configorconfig. - Added
registry-configworkspace to OCIArtifact and HarborOCIArtifact ResourceInterfaces. The legacydocker-credentialsworkspace is now deprecated but remains functional for backward compatibility. It will be removed in a future release.
Security updates
Updated base images, dependencies, and resolved security vulnerabilities
Breaking Changes
No breaking changes.
Fixed Issues
No issues in this release.
Known Issues
No issues in this release.
v1.7.0
Features and Enhancements
- Support integration with SonarQube and SonarCloud by using SonarQube Connector. more details:
- Support to deploy the Connectors system in a high availability (HA) configuration to ensure service continuity and fault tolerance. more details:
Breaking Changes
- When using the built-in forward proxy, proxy authentication information must be included.
Fixed Issues
No issues in this release.
Known Issues
No issues in this release.
v1.6.2
Features and Enhancements
- Security updates: Updated base images, dependencies, and resolved security vulnerabilities.
Fixed Issues
- Before this update, the Connector forward proxy MITM-intercepted every HTTPS CONNECT request. As a result, in Tekton buildah task Containerfile RUN steps, requests to non-connector destinations such as curl, apt-get, and wget were also routed through the MITM proxy, forcing clients to trust the proxy CA even when the traffic did not need Connector interception. This caused major friction for buildah-based builds. With this update, the forward proxy chooses behavior based on whether the target matches a connector address: requests to connector addresses continue to use MITM with auth injection, while requests to non-connector addresses fall back to a transparent tunnel so the client sees the real upstream certificate and no proxy CA trust is required. This preserves proxy behavior for connector traffic while avoiding the incorrect CA requirement for unrelated HTTPS requests.
- Before this update, when ConnectorsHarbor or ConnectorsOCI was deployed with NodePort exposure, the generated ConnectorClass could lose its openapi definition, so the Pipeline creation page could not load the Harbor/OCI project and repository options. With this update, the issue has been fixed, and the ConnectorClass keeps the full OpenAPI definition in NodePort deployments, allowing the related dropdown options to load normally.
Known Issues
No issues in this release.
v1.6.0 (LTS)
Features and Enhancements
More Connectors
- Support integration with GitLab Server by using GitLab Connector. more details:
- Support integration with NPM Registries by using NPM Connector. more details:
- Support integration with Harbor Registries by using Harbor Connector. more details:
ResourceInterface for Pipeline Integration
- Provides out-of-the-box definitions for
GitCodeRepository,OCIArtifact, andMavenArtifactresources, enabling seamless integration of external resources (Git repositories, OCI artifacts, Maven artifacts) into TektonCD pipelines through a unified UI interface. For more details, see - Support Dynamic Form in ResourceInterface for Pipeline Integration. For more details, see ResourceInterface Dynamic Form.
Connector API Enhancement
- Support accessing tool's original API through the Connector API when the ConnectorClass provides Proxy Service capabilities. The system now supports two ways to access tool resources: using the tool's original API via Proxy Service, or using custom APIs provided for the ConnectorClass. For more details, see Connector API.
ConnectorClass Customization Flexibility
- Support using Rego rules to extract tokens from client requests when using the built-in HTTP reverse proxy. Combined with the existing ability to inject authentication credentials into backend requests through Rego rules, you can now extend the built-in reverse proxy's capabilities to support tools with non-standard HTTP authentication mechanisms.
- For token extraction configuration, see Custom Rego-based Authentication.
- For authentication injection configuration, see Injecting Authentication Credentials into Backend Request when using built-in Reverse Proxy.
- Support using request variables in
spec.auth.types[].generator.regoto inject authentication credentials into backend requests. more details: Variables Available in Rego.
OCI Connector Forward Proxy
- OCI Connector supports using forward proxy for image operations. For more details, see OCI Connector Forward Proxy.
CSI Driver Built-in Configurations
Connectors CSI Driverprovides built-in configuration files that are always mounted into Pods. For more details, see Built-in Configurations.
Other Enhancements
- Add docs to explain credential permissions required for each connector. more details: Credential Permissions Required.
Breaking Changes
- Remove the
input.xxxvariable fromspec.auth.types[].generator.rego. Useinput.data.xxxinstead.
Fixed Issues
No issues in this release.
Known Issues
- Before this update, the Connector forward proxy MITM-intercepted every HTTPS CONNECT request. As a result, in Tekton buildah task Containerfile RUN steps, requests to non-connector destinations such as curl, apt-get, and wget were also routed through the MITM proxy, forcing clients to trust the proxy CA even when the traffic did not need Connector interception. This caused major friction for buildah-based builds. With this update, the forward proxy chooses behavior based on whether the target matches a connector address: requests to connector addresses continue to use MITM with auth injection, while requests to non-connector addresses fall back to a transparent tunnel so the client sees the real upstream certificate and no proxy CA trust is required. This preserves proxy behavior for connector traffic while avoiding the incorrect CA requirement for unrelated HTTPS requests.