feat: Add package registry to eck #8800

tehbooom · 2025-08-20T20:47:41Z

Elastic Package Registry (EPR) has been highly requested to be added to ECK.

EPR does not have any references since it does not require a license nor any other application.

The following was implemented for EPR

defaults to TLS
Sets the default container image to docker.elastic.co/package-registry/distribution
Users can set their own images
Users can update the config following the reference
Kibana can reference the EPR like Elasticsearch and Enterprise Search
If Kibana references EPR and TLS is enabled it will populate xpack.fleet.registryUrl and set the environment variable NODE_EXTRA_CA_CERTS to the path of EPR's CA which is mounted
If a user provides their own NODE_EXTRA_CA_CERTS with a mount the controller will combine the certs appending the EPR's CA to the users specified CA

This was tested with and without setting NODE_EXTRA_CA_CERTS using the below manifest

apiVersion: epr.k8s.elastic.co/v1alpha1
kind: ElasticPackageRegistry
metadata:
  name: registry
spec:
  version: 9.1.2
  count: 1
  podTemplate:
    spec:
      containers:
      - name: package-registry
        image: docker.elastic.co/package-registry/distribution:lite-9.1.2
---
apiVersion: elasticsearch.k8s.elastic.co/v1
kind: Elasticsearch
metadata:
  name: elasticsearch
spec:
  version: 9.1.2
  nodeSets:
  - name: default
    count: 1
---
apiVersion: kibana.k8s.elastic.co/v1
kind: Kibana
metadata:
  name: kibana
spec:
  version: 9.1.2
  count: 1
  elasticsearchRef:
    name: elasticsearch
  packageRegistryRef:
    name: registry
  config:
    telemetry.optIn: false
    xpack.fleet.isAirGapped: true
    xpack.fleet.agents.elasticsearch.hosts: ["https://elasticsearch-es-http.default.svc:9200"]
    xpack.fleet.agents.fleet_server.hosts: ["https://fleet-server-agent-http.default.svc:8220"]
    xpack.fleet.packages:
      - name: system
        version: latest
      - name: elastic_agent
        version: latest
      - name: fleet_server
        version: latest
    xpack.fleet.agentPolicies:
      - name: Fleet Server on ECK policy
        id: eck-fleet-server
        namespace: default
        monitoring_enabled:
          - logs
          - metrics
        unenroll_timeout: 900
        package_policies:
        - name: fleet_server-1
          id: fleet_server-1
          package:
            name: fleet_server
  podTemplate:
    spec:
      containers:
      - name: kibana
        env:
        - name: NODE_EXTRA_CA_CERTS
          value: /custom/user/ca-bundle.crt
        volumeMounts:
        - name: custom-ca
          mountPath: /custom/user
          readOnly: true
      volumes:
      - name: custom-ca
        secret:
          secretName: user-custom-ca-secret
---
apiVersion: v1
kind: Secret
metadata:
  name: user-custom-ca-secret
  namespace: default
type: Opaque
data:
  ca-bundle.crt: LS0tLS1CRUdJTiBDRVJUSUZJQ0FURS0tLS0tCk1JSUZtVENDQTRHZ0F3SUJBZ0lVYjVrK2d6V3A5YjljWTV4bkhUcWZNdHFHUXIwd0RRWUpLb1pJaHZjTkFRRUwKQlFBd1hERUxNQWtHQTFVRUJoTUNXRmd4RlRBVEJnTlZCQWNNREVSbFptRjFiSFFnUTJsMGVURWNNQm9HQTFVRQpDZ3dUUkdWbVlYVnNkQ0JEYjIxd1lXNTVJRXgwWkRFWU1CWUdBMVVFQXd3UGRHVnpkQzVsYkdGemRHbGpMbU52Ck1CNFhEVEkxTURneU1ERTRNakl3T0ZvWERUTTFNRGd4T0RFNE1qSXdPRm93WERFTE1Ba0dBMVVFQmhNQ1dGZ3gKRlRBVEJnTlZCQWNNREVSbFptRjFiSFFnUTJsMGVURWNNQm9HQTFVRUNnd1RSR1ZtWVhWc2RDQkRiMjF3WVc1NQpJRXgwWkRFWU1CWUdBMVVFQXd3UGRHVnpkQzVsYkdGemRHbGpMbU52TUlJQ0lqQU5CZ2txaGtpRzl3MEJBUUVGCkFBT0NBZzhBTUlJQ0NnS0NBZ0VBMHljTGVySWR3LzdpbGlKMzVBUEZ4bUx6TFRnNWRhUStWSUttS2lNbStlTTYKanJOY3lnbGphNVFEbHYvMStGUm5hamhrRTBobHoycXEzTjk0U1pYN3M2eHBnQUVzMGVQQ3VaZVBNU2VUYlYyRgp0YlIxNnFuM0JjenVxN3laOXZwdHR3MmJRdkJkY3JzZFU4T2RYUWhGNFd4QUFwODRKYWlMNmkzMlA2K2VPODBwCmh3Z1kwS0F1bzZoZC8zaFpNME14M2MwRmJmU0JHaTUyOHZKODYzUDRXZlEwMWdtUUxVbGl0UlhhTUhiaDRXSm0KOU45c0psUXpnbkNuQjZ6YkZjZ2gweWxrakd0UzBIZEo3eSs3dmE0Q1BqdkxlWGpwTnZuQzRjTmlocnp4Wmw5bQphM0ZVdVpiU0lRekE2ZFlkdkdrT2V3OTJEek1BaTdldU14UDdyYVhRejZmc1N6U1V4N1RjQWl5M2E5VU9Fdi9rCk5NV3VTbDlUMHRRSkhJSzJMc0t0MlVKWVVHWk4wOWU2SUVSTlJOL0FIUjVDbTlhcVQ1Q2ZyQW9JVVhNdUg2S1oKN1JCZFFockRxL2xEQk54bWs5dW44V2lic0NSVnkvVXRJQ3lOSytxbGpGUWZEd01hNkRkd3BjcnpnTWZnU3RTawpLek1LRUJla2N0Q0Q4dHNmTjZYem5USmNBYUJETzFlQWZyT0Z2NG1PTXJqVG90OEYvK3pxN0dXNTlqWTRvdFhMCkY3TnpadFl0eWsvbDRvb2hUZUFuM1ptd1BDMGJFQ1FkTmpTVkZ6ZXJCamE4ZjhacGpKRzNjUllyVmh6YUNsRWMKRU5wbFRHcldVaUVwRDdnTnNlNWNDSnZpQU12NHdwait2QTVVNlA3Z0MxUUtKV2hWS3BVYWcvTmtTSUFCRmtrQwpBd0VBQWFOVE1GRXdIUVlEVlIwT0JCWUVGTWdldEVJajZtRWdsZURGNkVNdUY4NXVnYzdZTUI4R0ExVWRJd1FZCk1CYUFGTWdldEVJajZtRWdsZURGNkVNdUY4NXVnYzdZTUE4R0ExVWRFd0VCL3dRRk1BTUJBZjh3RFFZSktvWkkKaHZjTkFRRUxCUUFEZ2dJQkFEOFU3dm1yWmhHTUZiV2YzRDZlNy84TUwzWEhLRk5TNy9UeWF3U2tvdGVSTVdFbgp1RWhQK2dmbkdUT2ZITFlQeHl5eEJ4U041T29sZHRJclo5dnhBc2dlYWJzSkJaenhQVHpxU09VN3h3b09LcTlRCmdKRUYxL0ZmemFlR1V5dVE2S1ZaZ0QvZ1JPSW42Ri9OUGlzM1pvbUpPOStuVWdTTnNiUm9RYmdPUGdPV3Q3Z1gKVEhuOHJpdUp2OXRPNFBRN09Sa3pubDJYbERlcE9xNVpwSUtkcVl0Rm5MUjF3SllyREZESmt0Q3h6MzFob0FrZwpSVjlSU1BSMFFxZ1JQeFNpNGpXdkNGUk5XTUFJc0NadGJsWExRRUljWGI1YnlsWXV2a3psTTJ4dHlHK3FaRFhMCnFoZDVNeFZIUkpqTzE1VEdpZXFRcUpMVkZyVElhTHFoaXZpQ1pUbDJoVkYxVlpPVG05MU5aeE53M25RL3JyeDgKK2VQV2xTWlZKWXc3SDRkWkx5WTFjRUxLT0YrZDJybVNSZ2pWaHZycUZ3R1M3MUQzYkV4Y0dSakNrOHNQWEZyRwpsOFRzY05RMXBPSGVuNlJhOFhVdGtxU1doZllFb3owZjBEem4wYmt4c2VWaCttS1BHV3QxcHdlemVFTFVwaHE3CmwwSVRLeis1b1lqYWVHTDRia25kcWlpemwzWkc2N0lYL3VyR0dQVUxkLzU1NEtRMFFPMS92S3Y2dE1YMWc0dVMKWHdWc0pzQjlrTUIwRFFxbDhRYmg0UEJ2ZW9RRTZvL3BycXRtWjR1RWdDMCt1cm5paDlCY1FweFNKOUljR1kxTQpBQzRBcG5Pem1CYTFhUVBMcDRaRFIxQXpFK1hXWDd2WWNWYUxleUJxRzRja3dwbUtOUnhpcnJjS2NaMkYKLS0tLS1FTkQgQ0VSVElGSUNBVEUtLS0tLQo=
---
apiVersion: agent.k8s.elastic.co/v1alpha1
kind: Agent
metadata:
  name: fleet-server
spec:
  version: 9.1.2
  kibanaRef:
    name: kibana
  elasticsearchRefs:
  - name: elasticsearch
  mode: fleet
  fleetServerEnabled: true
  policyID: eck-fleet-server
  deployment:
    replicas: 1
    podTemplate:
      spec:
        serviceAccountName: fleet-server
        automountServiceAccountToken: true
        resources:
          requests:
            cpu: 200m
            memory: 1Gi
          limits:
            cpu: 1
            memory: 2Gi
---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
  name: fleet-server
  namespace: default
rules:
- apiGroups: [""]
  resources:
  - pods
  - namespaces
  - nodes
  verbs:
  - get
  - watch
  - list
- apiGroups: ["apps"]
  resources:
    - replicasets
  verbs:
    - get
    - watch
    - list
- apiGroups: ["batch"]
  resources:
    - jobs
  verbs:
    - get
    - watch
    - list
- apiGroups: ["coordination.k8s.io"]
  resources:
  - leases
  verbs:
  - get
  - create
  - update
---
apiVersion: v1
kind: ServiceAccount
metadata:
  name: fleet-server
  namespace: default
---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
  name: fleet-server
  namespace: default
subjects:
- kind: ServiceAccount
  name: fleet-server
  namespace: default
roleRef:
  kind: ClusterRole
  name: fleet-server
  apiGroup: rbac.authorization.k8s.io

prodsecmachine · 2025-08-20T20:47:54Z

🎉 Snyk checks have passed. No issues have been found so far.

✅ security/snyk check is complete. No issues have been found. (View Details)

✅ license/snyk check is complete. No issues have been found. (View Details)

github-actions · 2025-08-20T20:48:46Z

🔍 Preview links for changed docs

docs/reference/api-reference/main.md

jsoriano

Took a quick look from the side of the team maintaining Package Registry.

It looks great, thanks for adding support for package registry in ECK, this will help many users.

Added some comments, please let us know if you need a more in-depth review from our side.

pkg/controller/packageregistry/controller.go

pkg/controller/kibana/initcontainer/fs_scripts.go

pkg/controller/packageregistry/config.go

jsoriano · 2025-08-25T09:30:35Z

pkg/controller/common/container/container.go

 	AgentImage            Image = "elastic-agent/elastic-agent"
 	MapsImage             Image = "elastic-maps-service/elastic-maps-server"
 	LogstashImage         Image = "logstash/logstash"
+	PackageRegistryImage  Image = "package-registry/distribution"


Is there an image used by default, or setting the image is required?

Yes the default version is package-registry/distribution:<version> where the user specifies the version. Version is a required field so if they do not specify one it will fail. Something I thought about was adding a epr_type or something like that where the user could specify the different EPR versions we publish. Like 9.1.2, lite-9.1.2, production, and lite. However I think its just as easy to specify the image in the template if you want something other than package-registry/distribution:<version>

While doing a first test I just realized that the default image is around ~5Gb 😅 (I was wondering why my container was not starting 🙃 ). I'm also wondering if it would not make sense to have short flag to select the image "type".

Edit: I just had a Pod that failed to start with the following error on GKE:

Warning Failed 90s kubelet Failed to pull image "docker.elastic.co/package-registry/distribution:9.1.0": failed to pull and unpack image "docker.elastic.co/package-registry/distribution:9.1.0": failed to extract layer sha256:0f0888ef6ac576c67e3a9acf8ec7216533b7f3144aeb14c9b93d0db9469830cd: write /var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/889/fs/packages/package-storage/security_detection_engine-9.0.9-beta.1.zip: no space left on device: unknown

I also had disk pressure conditions. I think the image size should be highlighted in the documentation so that K8s nodes can handle it.

Edit 2: This maybe also means that we need to check the disk size on the nodes used for our e2e tests

@jsoriano do you think we should change the default image to be something smaller? I selected this image because it is what we recommend.

Yeah, the lite images were added as smaller images for this kind of use cases, but even this image is starting to be too big.

There are vanilla images that don't contain any package. They fail to start if no directory with packages is configured, but they can also be configured in proxy mode, to forward requests for example to the public EPR.

Latest of these images is docker.elastic.co/package-registry/package-registry:v1.31.1.

There is an open issue about allowing to start even if no package is available yet: elastic/package-registry#1351.

More about the proxy mode in https://github.com/elastic/package-registry/?tab=readme-ov-file#proxy-mode.

We also have a WIP to create custom distributions, and smaller images elastic/package-registry#1335.

pkg/controller/packageregistry/config.go

Copilot

Pull Request Overview

This PR adds Elastic Package Registry (EPR) support to ECK, introducing a new CRD for deploying EPR instances and enabling Kibana to reference EPR instances for Fleet package management.

Adds ElasticPackageRegistry CRD with controller to manage EPR deployments
Enables Kibana to associate with EPR instances via packageRegistryRef field
Implements TLS certificate handling and CA mounting for secure communication between Kibana and EPR

Reviewed Changes

Copilot reviewed 60 out of 61 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
`pkg/apis/epr/v1alpha1/`	New API definitions for ElasticPackageRegistry CRD
`pkg/controller/packageregistry/`	Controller implementation for managing EPR resources
`pkg/controller/association/controller/kibana_epr.go`	Association controller for Kibana-EPR relationships
`pkg/apis/kibana/v1/kibana_types.go`	Adds packageRegistryRef field and EPR association support
`pkg/controller/kibana/`	Updates Kibana controller to handle EPR associations and CA certificates
`test/e2e/`	E2E tests for EPR functionality and associations

Comments suppressed due to low confidence (1)

pkg/controller/kibana/pod_test.go:1

The comment on line 67 says 'readinessProbe is the readiness probe for the maps container' but this function is in the packageregistry controller and should refer to the package registry container.

// Copyright Elasticsearch B.V. and/or licensed to Elasticsearch B.V. under one

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

pkg/apis/epr/v1alpha1/labels.go

pkg/controller/packageregistry/labels.go

pkg/apis/epr/v1alpha1/epr_types_test.go

barkbay · 2025-09-08T06:15:08Z

@tehbooom 👋 please let me know when you need another review, thanks!

tehbooom · 2025-09-08T13:12:10Z

@tehbooom 👋 please let me know when you need another review, thanks!

@barkbay

Added EPR to ECK diagnostics here.

I still need to update our documentation. I know we changed how we do documentation so if you could please point me in the right direction where ECK docs live that would be great. This PR is ready for another review. Thanks!

barkbay · 2025-09-15T06:14:50Z

I still need to update our documentation. I know we changed how we do documentation so if you could please point me in the right direction where ECK docs live that would be great. This PR is ready for another review. Thanks!

Documentation has moved here: https://github.com/elastic/docs-content Please note that the main branch of that repo is immediately published, therefore do not merge the doc PR until the feature has been released.

I'll try to take another look to your PR this week, I'm struggling to keep up with the pace of PRs opened in this repo 😅

barkbay · 2025-09-16T09:38:10Z

buildkite test this -f p=gke,E2E_TAGS=epr

barkbay · 2025-09-16T10:00:20Z

buildkite test this -f p=gke,E2E_TAGS=epr

barkbay · 2025-09-16T10:49:04Z

E2E tests are still failing with:

  Warning  Failed               12m   kubelet            Failed to pull image "docker.elastic.co/package-registry/distribution:9.1.2": failed to pull and unpack image "docker.elastic.co/package-registry/distribution:9.1.2": failed to extract layer sha256:57bbe197467b8b19ba0705f05ee41860ff3bb44020ed5986df96bfed4614e630: write /var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/396/fs/packages/package-storage/security_detection_engine-8.6.8.zip: no space left on device

We also have to find a solution for this. IIUC elastic/package-registry#1335 would be the way to go? I'll also try to check if we can increase the disk on GKE nodes, but it would still mean that we may have to skip other providers (AWS, Azure, Kind...).

IIUC the image currently requires ~14Gi:

docker.elastic.co/package-registry/distribution                                       9.1.2                                             d127b26dc3000       13.8GB

barkbay

~~Pods are being recreated in my dev env because of changes in packageregistry.k8s.elastic.co/config-hash while I do nothing:~~

Edit: Nevermind, it's because I used short lived certificates to test certificate rotation, and it seems it requires the Pod to be recreated. @tehbooom Could you confirm that certificates are not hot reloaded?

pkg/apis/epr/v1alpha1/labels.go

barkbay · 2025-09-16T15:23:58Z

pkg/controller/kibana/initcontainer/fs_scripts.go

+if [[ -f "` + volume.EPRCACertPath + `" ]]; then
+	echo "EPR CA certificate found, checking for user-provided CA bundle..."
+	
+	# Check if user provided their own NODE_EXTRA_CA_CERTS (from init container env)


Would it make things easier to implement and debug if we ask the users to not use NODE_EXTRA_CA_CERTS but instead allow them to add custom certificates using an alternate env. variable, for example KIBANA_EXTRA_CA_CERTS (I'm asking because the way we handle NODE_EXTRA_CA_CERTS feels a bit "hacky" to me tbh)

I think one issue with that would be that there might be already users that we would break if we stopped supporting user defined NODE_EXTRA_CA_CERTS

I think one issue with that would be that there might be already users that we would break if we stopped supporting user defined NODE_EXTRA_CA_CERTS

Agreed. However, if we did use KIBANA_EXTRA_CA_CERTS what would it make it easier to debug and implement? You are still checking if the user provided extra CAs.

naemono

Initial look at this I failed to submit previously.

config/crds/v1/resources/kibana.k8s.elastic.co_kibanas.yaml

naemono · 2025-08-25T18:45:31Z

config/crds/v1/resources/kibana.k8s.elastic.co_kibanas.yaml

+                  secretName:
+                    description: |-
+                      SecretName is the name of an existing Kubernetes secret that contains connection information for associating an
+                      Elastic resource not managed by the operator.
+                      The referenced secret must contain the following:
+                      - `url`: the URL to reach the Elastic resource
+                      - `username`: the username of the user to be authenticated to the Elastic resource
+                      - `password`: the password of the user to be authenticated to the Elastic resource
+                      - `ca.crt`: the CA certificate in PEM format (optional)
+                      - `api-key`: the key to authenticate against the Elastic resource instead of a username and password (supported only for `elasticsearchRefs` in AgentSpec and in BeatSpec)
+                      This field cannot be used in combination with the other fields name, namespace or serviceName.
+                    type: string
+                  serviceName:
+                    description: |-
+                      ServiceName is the name of an existing Kubernetes service which is used to make requests to the referenced
+                      object. It has to be in the same namespace as the referenced resource. If left empty, the default HTTP service of
+                      the referenced resource is used.


Are these needed?

secretName is not needed. Is there a another way to do an association without commonv1.ObjectSelector ?

I think it is an acceptable compromise to use ObjectSelector here even if it has elements that do not apply. The alternative would be to introduce a custom struct and then translate to ObjectSelector in the functions required by the Association interface.

Are we okay with resolving this even though it doesnt need secretName?

config/crds/v1/resources/kibana.k8s.elastic.co_kibanas.yaml

config/recipes/packageregistry/02-es-kb.yaml

config/webhook/manifests.yaml

pebrc

Approach looks reasonable with one exception: I am also not a big fan of of the NODE_EXTRA_CA_CERTS init container hackery but don't see a good alternative right now if we want to be backwards compatible.

Main blocker to merge this imo is the lack of UBI images for the package registry.

I could not get the recommended default image to work, as the k8s nodes in my environment ran out of ephemeral storage while trying to pull the image. I wonder how viable this image is for any environment? I was successful with the lite image though.

deploy/eck-stack/charts/eck-package-registry/templates/epr.yaml

deploy/eck-stack/charts/eck-package-registry/values.yaml

pkg/apis/common/v1/association.go

pkg/controller/association/controller/kibana_epr.go

pebrc · 2025-09-22T09:18:59Z

pkg/controller/kibana/initcontainer/fs_scripts.go

+if [[ -f "` + volume.EPRCACertPath + `" ]]; then
+	echo "EPR CA certificate found, checking for user-provided CA bundle..."
+	
+	# Check if user provided their own NODE_EXTRA_CA_CERTS (from init container env)


I think one issue with that would be that there might be already users that we would break if we stopped supporting user defined NODE_EXTRA_CA_CERTS

tehbooom

Ive update the test image to be the lite image since others have stated it works with that image

tehbooom · 2025-09-22T13:03:25Z

pkg/controller/kibana/initcontainer/fs_scripts.go

+#############################
+
+# Handle EPR CA certificate consolidation with user-provided NODE_EXTRA_CA_CERTS
+# This must run before the early exit to ensure certificates are always processed


I don't remember the scenario as its been sometime. But putting this after the check to see if it was already initialized would give me x509 errors. I think it was if I added EPR after Kibana was already deployed it wouldnt pick up the new certificate.

tehbooom · 2025-09-22T13:04:59Z

pkg/controller/kibana/initcontainer/fs_scripts.go

+if [[ -f "` + volume.EPRCACertPath + `" ]]; then
+	echo "EPR CA certificate found, checking for user-provided CA bundle..."
+	
+	# Check if user provided their own NODE_EXTRA_CA_CERTS (from init container env)


I think one issue with that would be that there might be already users that we would break if we stopped supporting user defined NODE_EXTRA_CA_CERTS

Agreed. However, if we did use KIBANA_EXTRA_CA_CERTS what would it make it easier to debug and implement? You are still checking if the user provided extra CAs.

tehbooom · 2025-09-22T13:17:09Z

config/crds/v1/resources/kibana.k8s.elastic.co_kibanas.yaml

+                  secretName:
+                    description: |-
+                      SecretName is the name of an existing Kubernetes secret that contains connection information for associating an
+                      Elastic resource not managed by the operator.
+                      The referenced secret must contain the following:
+                      - `url`: the URL to reach the Elastic resource
+                      - `username`: the username of the user to be authenticated to the Elastic resource
+                      - `password`: the password of the user to be authenticated to the Elastic resource
+                      - `ca.crt`: the CA certificate in PEM format (optional)
+                      - `api-key`: the key to authenticate against the Elastic resource instead of a username and password (supported only for `elasticsearchRefs` in AgentSpec and in BeatSpec)
+                      This field cannot be used in combination with the other fields name, namespace or serviceName.
+                    type: string
+                  serviceName:
+                    description: |-
+                      ServiceName is the name of an existing Kubernetes service which is used to make requests to the referenced
+                      object. It has to be in the same namespace as the referenced resource. If left empty, the default HTTP service of
+                      the referenced resource is used.


secretName is not needed. Is there a another way to do an association without commonv1.ObjectSelector ?

pebrc · 2025-09-25T10:01:09Z

buildkite test this -f p=gke,E2E_TAGS=epr

feat: Add package registry to eck

3aa3bb0

botelastic bot added the triage label Aug 20, 2025

github-actions bot deployed to docs-preview August 20, 2025 20:48 View deployment

fix: remove kibana ref in EPR

65e6240

github-actions bot deployed to docs-preview August 21, 2025 12:32 View deployment

fix: Add EPR rbac

7fba84c

github-actions bot deployed to docs-preview August 21, 2025 14:35 View deployment

tehbooom added 2 commits August 22, 2025 12:00

fix: Add e2e tests for epr and kb

8867801

docs: add examples for epr

6e768be

github-actions bot deployed to docs-preview August 22, 2025 16:01 View deployment

fix: linting

d384127

github-actions bot deployed to docs-preview August 22, 2025 16:40 View deployment

jsoriano reviewed Aug 25, 2025

View reviewed changes

pebrc requested a review from Copilot August 25, 2025 15:17

This comment was marked as outdated.

Sign in to view

tehbooom added 4 commits August 25, 2025 12:27

fix: Set minimum version for EPR which is 7.15.1

7f0201e

fix: remove references to Maps Server

8eee0bf

test: increase timeout for e2e

ba2554c

fix: Update the minimum supported version for EPR which is 7.15.1

38b08a7

github-actions bot deployed to docs-preview August 25, 2025 17:03 View deployment

naemono requested a review from Copilot August 25, 2025 18:39

naemono added >enhancement Enhancement of existing functionality discuss We need to figure this out labels Aug 25, 2025

botelastic bot removed the triage label Aug 25, 2025

Copilot AI reviewed Aug 25, 2025

View reviewed changes

pkg/apis/epr/v1alpha1/labels.go Show resolved Hide resolved

pkg/controller/packageregistry/labels.go Outdated Show resolved Hide resolved

pkg/apis/epr/v1alpha1/epr_types_test.go Outdated Show resolved Hide resolved

test: revert test timeout

98d088d

barkbay added >feature Adds or discusses adding a feature to the product and removed >enhancement Enhancement of existing functionality labels Aug 26, 2025

fix: make generate docs

9a1a9f1

github-actions bot deployed to docs-preview August 29, 2025 12:40 View deployment

tehbooom mentioned this pull request Sep 8, 2025

feat: add epr to diag elastic/eck-diagnostics#346

Open

barkbay added the release-highlight Candidate for the ECK release highlight summary label Sep 15, 2025

Merge remote-tracking branch 'origin/main' into epr

5ad2812

github-actions bot deployed to docs-preview September 16, 2025 09:30 View deployment

barkbay added 2 commits September 16, 2025 11:59

fix unit tests

2923f91

s/9.0.0/9.1.2

04d47cf

github-actions bot deployed to docs-preview September 16, 2025 10:00 View deployment

barkbay reviewed Sep 16, 2025

View reviewed changes

pkg/apis/epr/v1alpha1/labels.go Outdated Show resolved Hide resolved

barkbay reviewed Sep 16, 2025

View reviewed changes

naemono reviewed Sep 16, 2025

View reviewed changes

pebrc reviewed Sep 22, 2025

View reviewed changes

tehbooom added 7 commits September 22, 2025 09:43

fix: remove references to kibana

def340a

fix: Remove unused function

eb79598

fix: label name

5293ffc

fix: remove beta

5fa0acf

fix: spelling

275755a

fix: update function name

bcf264f

test: use smaller container image during tests

8725575

github-actions bot deployed to docs-preview September 22, 2025 13:46 View deployment

tehbooom commented Sep 22, 2025

View reviewed changes

feat: Add package registry to eck #8800

Are you sure you want to change the base?

feat: Add package registry to eck #8800

Uh oh!

Conversation

tehbooom commented Aug 20, 2025

Uh oh!

prodsecmachine commented Aug 20, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

🎉 Snyk checks have passed. No issues have been found so far.

Uh oh!

github-actions bot commented Aug 20, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

🔍 Preview links for changed docs

Uh oh!

jsoriano left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

barkbay Aug 26, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

This comment was marked as outdated.

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull Request Overview

Reviewed Changes

Uh oh!

Uh oh!

Uh oh!

Uh oh!

barkbay commented Sep 8, 2025

Uh oh!

tehbooom commented Sep 8, 2025

Uh oh!

barkbay commented Sep 15, 2025

Uh oh!

barkbay commented Sep 16, 2025

Uh oh!

barkbay commented Sep 16, 2025

Uh oh!

barkbay commented Sep 16, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

barkbay left a comment • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

barkbay Sep 16, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

naemono left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

prodsecmachine commented Aug 20, 2025 •

edited

Loading

github-actions bot commented Aug 20, 2025 •

edited

Loading

barkbay Aug 26, 2025 •

edited

Loading

barkbay commented Sep 16, 2025 •

edited

Loading

barkbay left a comment •

edited

Loading

barkbay Sep 16, 2025 •

edited

Loading

tehbooom Sep 22, 2025 •

edited

Loading