Back-off pulling image "public.ecr.aws/opsterio/opensearch-operator:2.3.1"[BUG] #709

vkumar85 · 2024-01-25T15:35:22Z

What is the bug?

A clear and concise description of the bug.

Did anything change with the location of this image reccently?

How can one reproduce the bug?

Steps to reproduce the behavior.

I am just trying to redeploy the helm chart.

What is the expected behavior?

A clear and concise description of what you expected to happen.

Image pull should be successful.

What is your host/environment?

Operating system, version.

Do you have any screenshots?

If applicable, add screenshots to help explain your problem.

Do you have any additional context?

Add any other context about the problem.

pomyslowynick · 2024-01-25T16:19:43Z

Looks like its ECR is down https://gallery.ecr.aws/opsterio/opensearch-operator

Rockawear · 2024-01-25T21:21:37Z

Seeing the same issues as well. it seems like this is Opster repository, do we know if OpenSearch has it's own repo with this image?

evheniyt · 2024-01-26T07:54:52Z

Looks like no, it is still not there https://hub.docker.com/u/opensearchproject
The task regarding the transfer is not resolved #674

mustafaonure · 2024-01-26T08:31:43Z

Seeing the same issues as well. Is there any solution for this issue? anyone know?

swoehrl-mw · 2024-01-26T09:46:21Z

If you can use version 2.4.0 (older images were not mirrored) you can get the image from the compatible MaibornWolff fork of the operator (https://github.com/MaibornWolff/opensearch-operator, ghcr.io/maibornwolff/opensearch-operator:2.4.0). Note that you will have to override image.tag and image.repository in the helm chart values as these still point to the ecr repo. The fork also already has a version 2.5.0 release.

salyh · 2024-01-26T10:05:39Z

Here is also a working fork https://github.com/eliatra/opensearch-k8s-operator from Eliatra

swoehrl-mw · 2024-01-26T10:48:42Z

Here is also a working fork https://github.com/eliatra/opensearch-k8s-operator from Eliatra

That is incompatible because Eliatra renamed all CRD apigroups.

rybnico · 2024-01-26T15:30:12Z

I found public.ecr.aws/opsterio/opensearch-operator:2.4.0 on one of my nodes, retagged it and pushed it to docker.io/rybnico/opensearch-operator:2.4.0. Feel free to use this identical image until this issue is solved. Maybe I can save someone's weekend :)

prudhvigodithi · 2024-01-26T17:50:00Z

Hey I dint expect the opster ECR repo to go down, I will be doing a quick release 2.5.0 release through opensearch-project/opensearch-k8s-operator with images pushed to opensearch-project docker and ECR accounts , this will also include revert of the PR that was pushed recently to refactor opster API's.
Tagging @swoehrl-mw, moving forward we can have a community meeting to discuss on next action items with the operator roadmap and if required we can backfill the past releases to opensearch-project docker and ECR accounts.
Thanks
@bbarani @peterzhuamazon

jashandeep-sohi · 2024-01-26T23:28:05Z

Consider also pushing/back-filling images to ghcr.io.

Here's a manually triggered workflow I'm using:

name: Backfill Container Image
run-name: ${{ inputs.tag }}
concurrency: ${{ inputs.tag }}

on:
 workflow_dispatch:
   inputs:
     tag:
        description: "Tag to checkout and build"
        required: true

env:
  REGISTRY: ghcr.io
  IMAGE_NAME: ${{ github.repository }}

permissions:
  contents: read
  packages: write

jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
        with:
          ref: refs/tags/${{ inputs.tag }}
          fetch-tags: true
      - uses: docker/setup-qemu-action@v3
      - uses: docker/setup-buildx-action@v3
      - uses: docker/login-action@v3
        with:
          registry: ${{ env.REGISTRY }}
          username: ${{ github.actor }}
          password: ${{ secrets.GITHUB_TOKEN }}
          
      - uses: docker/metadata-action@v5
        id: meta
        with:
          context: git
          images: ${{ env.REGISTRY }}/${{ env.IMAGE_NAME }}
          
      - name: Build and push
        uses: docker/build-push-action@v5
        with:
          context: opensearch-operator
          push: true
          platforms: linux/amd64,linux/arm,linux/arm64
          tags: ${{ steps.meta.outputs.tags }}
          labels: ${{ steps.meta.outputs.labels }}

Operator is uninstallable See issue opensearch-project/opensearch-k8s-operator#709

roskee · 2024-01-29T18:38:51Z

Any updates on this? I depended on the public.ecr.aws/opsterio/opensearch-operator:2.4.0 image. If there are any official alternatives, I would be more than happy to update 🙏

BobakMariusz · 2024-01-29T20:16:30Z

+1 Also facing same problem : public.ecr.aws/opsterio/opensearch-operator:2.4.0

sunsrin · 2024-01-29T20:50:36Z

Tried with :latest which was uploaded 2 hours back (along with 2.3.2) .. but the controller manager seems to be failing health check (might be unrelated) or my environment issue

prudhvigodithi · 2024-01-30T00:46:25Z

Hey Everyone, a quick update, at this point we are still working with opensearch-project opensource team to get some approvals to publish the images to opensearch-project dockerHub and ECR registries.
https://gallery.ecr.aws/opensearchproject/
https://hub.docker.com/u/opensearchproject
Thank you

agershman · 2024-01-31T18:51:56Z

Hey Everyone, a quick update, at this point we are still working with opensearch-project opensource team to get some approvals to publish the images to opensearch-project dockerHub and ECR registries. https://gallery.ecr.aws/opensearchproject/ https://hub.docker.com/u/opensearchproject Thank you

@prudhvigodithi This may be a known issue but I'm observing that multi-arch builds don't seem to be in place. E.g. I can pull a version the operator image but only linux/amd64 platform images appear to be available. This is problematic for cases where the underlying platform is linux/arm64:

docker pull --platform linux/arm64 public.ecr.aws/opsterio/opensearch-operator:2.4.0
2.4.0: Pulling from opsterio/opensearch-operator
Digest: sha256:e650adab28ebf1c96ea2b350727beb53de3520b55de37720b8e4fdbd6ed8e4f1
Status: Image is up to date for public.ecr.aws/opsterio/opensearch-operator:2.4.0
image with reference public.ecr.aws/opsterio/opensearch-operator:2.4.0 was found but does not match the specified platform: wanted linux/arm64, actual: linux/amd64

Inspecting the downloaded image and I can see that Architecture is amd64.

prudhvigodithi · 2024-01-31T18:56:42Z

Hey @agershman, the operator project is recently migrated to opensearch-project org, so we are working on publishing the images to following registries:

ECR: https://gallery.ecr.aws/opensearchproject/
Docker: https://hub.docker.com/u/opensearchproject

Once I got the approval I will go ahead and pushing the images and notify here.

jashandeep-sohi · 2024-01-31T19:12:56Z

Hey @agershman, the operator project is recently migrated to opensearch-project org, so we are working on publishing the images to following registries:

ECR: https://gallery.ecr.aws/opensearchproject/ Docker: https://hub.docker.com/u/opensearchproject

Once I got the approval I will go ahead and pushing the images and notify here.

Why not just push images to Github's registry? I don't think you need additional permissions/token setup. Github Actions are able to push to it just fine.

prudhvigodithi · 2024-01-31T20:15:46Z

Hey @jashandeep-sohi thanks, this is more than additional permissions/token setup etc, since now this project is part of the opensearch-project org, working with the opensource legal team to make sure the package licenses and images published are with open source licenses and are compliant.
Thanks

### Description Update `developing.md` and add `THIRD_PARTY_NOTICES` for repo compliance coming from OpenSearch open source team. ### Issues Resolved Part of #709 and #674 By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license. For more information on following Developer Certificate of Origin and signing off your commits, please check [here](https://github.com/opensearch-project/OpenSearch/blob/main/CONTRIBUTING.md#developer-certificate-of-origin). Signed-off-by: Prudhvi Godithi <[email protected]>

### Description Update Jenkinsfile to add ECR staging registry ### Issues Resolved Part of #709 and #674 By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license. For more information on following Developer Certificate of Origin and signing off your commits, please check [here](https://github.com/opensearch-project/OpenSearch/blob/main/CONTRIBUTING.md#developer-certificate-of-origin). Signed-off-by: Prudhvi Godithi <[email protected]>

mrvdcsg · 2024-02-01T21:48:07Z

I didn't see a comment on this thread yet but it appears that opster put 2 images back up on the ECR which resolved our issue (temporarily at least). If you are using 2.4.0 or 2.3.2, the images should pull successfully from https://gallery.ecr.aws/opsterio/opensearch-operator It is fair to say this is only a short-term work-around and they likely put it back up due to all the issues taking it down caused.

### Description Jenkinsfile bug and prepare for 2.5.0 release ### Issues Resolved Part of #709 and #674 By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license. For more information on following Developer Certificate of Origin and signing off your commits, please check [here](https://github.com/opensearch-project/OpenSearch/blob/main/CONTRIBUTING.md#developer-certificate-of-origin). Signed-off-by: Prudhvi Godithi <[email protected]>

prudhvigodithi · 2024-02-02T00:43:25Z

Released 2.5.0 version, the operator images now are part of official OpenSearch Project DockerHub and ECR registries.
https://gallery.ecr.aws/opensearchproject/opensearch-operator
https://hub.docker.com/r/opensearchproject/opensearch-operator/tags

Release build link: https://build.ci.opensearch.org/job/opensearch-operator-release/

Please test with opensearchproject/opensearch-operator:2.5.0 or public.ecr.aws/opensearchproject/opensearch-operator:2.5.0 and let me know if you see any issues.

Thanks
@bbarani @swoehrl-mw @peterzhuamazon

prudhvigodithi · 2024-02-02T01:38:38Z

There is a small bug with helm charts for 2.5.0, I have raised a PR to fix and release a small 2.5.1, but override the bug with 2.5.0 please run:

helm install my-opensearch-operator opensearch-operator/opensearch-operator --version 2.5.0 --set manager.image.repository=opensearchproject/opensearch-operator  --set manager.image.tag=2.5.0

Thanks you

### Description Prepare Release 2.5.1 ### Issues Resolved Part of #709 and #674 By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license. For more information on following Developer Certificate of Origin and signing off your commits, please check [here](https://github.com/opensearch-project/OpenSearch/blob/main/CONTRIBUTING.md#developer-certificate-of-origin). Signed-off-by: Prudhvi Godithi <[email protected]>

### Description Readme update ### Issues Resolved Part of #709 and #674 By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license. For more information on following Developer Certificate of Origin and signing off your commits, please check [here](https://github.com/opensearch-project/OpenSearch/blob/main/CONTRIBUTING.md#developer-certificate-of-origin). Signed-off-by: Prudhvi Godithi <[email protected]>

prudhvigodithi · 2024-02-02T23:38:50Z

Hey Everyone 2.5.1 is released. Please start using 2.5.1.

helm install my-opensearch-operator opensearch-operator/opensearch-operator --version 2.5.1

Thank you

@mrvdcsg @jashandeep-sohi @rybnico @vkumar85 @sunsrin @welkson @vipinjn24 @pomyslowynick @Rockawear @evheniyt @mustafaonure @swoehrl-mw @bbarani

welkson · 2024-02-03T12:38:00Z

@prudhvigodithi 2.5.1 version change API version?

k apply -f cluster-dev.yaml
Error from server (NotFound): error when creating "cluster-dev.yaml": the server could not find the requested resource (post opensearchclusters.opensearch.opster.io)

manifest file:

apiVersion: opensearch.opster.io/v1
kind: OpenSearchCluster
metadata:
  name: test-opensearch-dev
  namespace: test-opensearch-dev
spec:
  general:
    setVMMaxMapCount: true
    serviceName: opensearch-dev
    version: 2.11.1
    # monitoring: 
    #   enable: true 
    #   scrapeInterval: 30s 
    #   monitoringUserSecret: admin-credentials-secret # Optional, name of a secret with username/password for prometheus to acces the plugin metrics endpoint with, defaults to the admin user
    #   pluginUrl: https://github.com/aiven/prometheus-exporter-plugin-for-opensearch/releases/download/2.8.0.0/prometheus-exporter-2.8.0.0.zip
    # pluginsList: ["https://github.com/aiven/prometheus-exporter-plugin-for-opensearch/releases/download/2.8.0.0/prometheus-exporter-2.8.0.0.zip"]
  security:
    config:
      securityConfigSecret:
        name: securityconfig-secret
      adminCredentialsSecret:
        name: admin-credentials-secret
    tls:
       http:
         generate: true 
       transport:
         generate: true
         perNode: true    
  confMgmt:
    smartScaler: true
  dashboards:
    enable: true
    version: 2.11.1
    replicas: 1
    opensearchCredentialsSecret:
      name: admin-credentials-secret
    resources:
      requests:
          memory: "5Mi"
          cpu: "1m"
      limits:
          memory: "1Gi"
          cpu: "4"
  nodePools:
    - component: masters
      replicas: 3
      diskSize: "30Gi"
      jvm: -Xmx1024M -Xms1024M
      nodeSelector:
      resources:
          requests:
            memory: "2Gi"
            cpu: "2"
          limits:
            memory: "6Gi"
            cpu: "4"
      roles:
        - "cluster_manager"
      persistence:
        pvc:
          accessModes:
          - ReadWriteOnce
          storageClass: default-storageclass
    - component: data
      replicas: 3
      diskSize: "100Gi"
      jvm: -Xmx1024M -Xms1024M
      nodeSelector:
      resources:
          requests:
            memory: "2Gi"
            cpu: "2"
          limits:
            memory: "6Gi"
            cpu: "4"
      roles:
        - "data"
        - "ingest"
      persistence:
        pvc:
          accessModes:
          - ReadWriteOnce
          storageClass: default-storageclass
    - component: coordinating
      replicas: 1
      diskSize: "54Gi"
      jvm: -Xmx1024M -Xms1024M
      nodeSelector:
      resources:
          requests:
            memory: "2Gi"
            cpu: "2"
          limits:
            memory: "6Gi"
            cpu: "4"
      roles:
        - ""
      additionalConfig:
        node.master: "false"
        node.data: "false"
        node.ingest: "false"
        node.remote_cluster_client: "false"
      persistence:
        pvc:
          accessModes:
          - ReadWriteOnce
          storageClass: default-storageclass

Operator details:

 kubectl describe pod opensearch-operator-controller-manager-55dccbb9cf-s6wkr | grep image
  Normal  Pulling    6m19s  kubelet            Pulling image "gcr.io/kubebuilder/kube-rbac-proxy:v0.15.0"
  Normal  Pulled     6m9s   kubelet            Successfully pulled image "gcr.io/kubebuilder/kube-rbac-proxy:v0.15.0" in 9.386407301s
  Normal  Pulling    6m9s   kubelet            Pulling image "opensearchproject/opensearch-operator:2.5.1"
  Normal  Pulled     5m59s  kubelet            Successfully pulled image "opensearchproject/opensearch-operator:2.5.1" in 9.831331341s

> helm list
NAME               	NAMESPACE	REVISION	UPDATED                             	STATUS  	CHART                    	APP VERSION
opensearch-operator	default  	1       	2024-02-03 09:32:08.498251 -0300 -03	deployed	opensearch-operator-2.5.1	2.5.1

> k get crd | grep -i opensearch
opensearchactiongroups.opensearch.opster.io           2024-02-03T12:32:11Z
opensearchcomponenttemplates.opensearch.opster.io     2024-02-03T12:32:11Z
opensearchindextemplates.opensearch.opster.io         2024-02-03T12:32:11Z
opensearchismpolicies.opensearch.opster.io            2024-02-03T12:32:11Z
opensearchroles.opensearch.opster.io                  2024-02-03T12:32:11Z
opensearchtenants.opensearch.opster.io                2024-02-03T12:32:12Z
opensearchuserrolebindings.opensearch.opster.io       2024-02-03T12:32:12Z
opensearchusers.opensearch.opster.io                  2024-02-03T12:32:12Z

Reverting to 2.5.0:

$ helm uninstall opensearch-operator

$ helm install opensearch-operator opensearch-operator/opensearch-operator --version 2.5.0 --set manager.image.repository=opensearchproject/opensearch-operator  --set manager.image.tag=2.5.0

$ k get crd | grep -i opensearch
opensearchactiongroups.opensearch.opster.io           2024-02-03T12:54:46Z
opensearchclusters.opensearch.opster.io               2024-02-03T12:54:46Z    <------------- 
opensearchcomponenttemplates.opensearch.opster.io     2024-02-03T12:54:46Z
opensearchindextemplates.opensearch.opster.io         2024-02-03T12:54:46Z
opensearchismpolicies.opensearch.opster.io            2024-02-03T12:54:46Z
opensearchroles.opensearch.opster.io                  2024-02-03T12:54:46Z
opensearchtenants.opensearch.opster.io                2024-02-03T12:54:46Z
opensearchuserrolebindings.opensearch.opster.io       2024-02-03T12:54:46Z
opensearchusers.opensearch.opster.io                  2024-02-03T12:54:46Z

agershman · 2024-02-03T18:17:59Z

@prudhvigodithi I wanted to circle back on my earlier comment. I'm seeing that the reestablished helm chart and referenced image at version 2.5.1 does indeed include multi-arch support (e.g. linux/amd64 and linux/arm64). What I am however not seeing is that previous existing versions (e.g. 2.4.0) do not include much-arch support (i.e. only linux/amd64 appears to be back in place). This forces folks who were using/pinned on 2.4.0 to upgrade to 2.5.1. Is this expected or is there still ongoing work to get multi-arch builds retroactively created for versions < 2.5.1?

prudhvigodithi · 2024-02-03T18:31:36Z

Hey @welkson, there is no change in API's, I was able to see the crd opensearchclusters.opensearch.opster.io

helm install my-opensearch-operator opensearch-operator/opensearch-operator --version 2.5.1
NAME: my-opensearch-operator
LAST DEPLOYED: Sat Feb  3 10:30:17 2024
NAMESPACE: default
STATUS: deployed
REVISION: 1
TEST SUITE: None

k get crd | grep -i "opensearchclusters.opensearch.opster.io"
opensearchclusters.opensearch.opster.io             2024-02-03T18:30:32Z

I have also tested the following and was able to start the cluster

apiVersion: opensearch.opster.io/v1
kind: OpenSearchCluster
metadata:
  name: pgcluster
  namespace: default
spec:
  security:
    config: 
    tls:
       http:
         generate: true 
       transport:
         generate: true
         perNode: true
  general:
    httpPort: 9400
    serviceName: my-first-cluster
    version: 2.11.0
    pluginsList: ["https://github.com/aiven/prometheus-exporter-plugin-for-opensearch/releases/download/2.11.0.0/prometheus-exporter-2.11.0.0.zip"]
    drainDataNodes: true
  dashboards:
    version: 2.11.0
    enable: true
    replicas: 1
    resources:
      requests:
         memory: "512Mi"
         cpu: "200m"
      limits:
         memory: "512Mi"
         cpu: "200m"
  nodePools:
    - component: masters
      replicas: 3
      additionalConfig:
        path.repo: '["/tmp/snapshots"]'
      resources:
         requests:
            memory: "1Gi"
            cpu: "550m"
         limits:
            memory: "1Gi"
            cpu: "550m"
      roles:
        - "data"
        - "cluster_manager"
      persistence:
         emptyDir: {}

prudhvigodithi · 2024-02-03T18:37:15Z

@prudhvigodithi I wanted to circle back on my earlier comment. I'm seeing that the reestablished helm chart and referenced image at version 2.5.1 does indeed include multi-arch support (e.g. linux/amd64 and linux/arm64). What I am however not seeing is that previous existing versions (e.g. 2.4.0) do not include much-arch support (i.e. only linux/amd64 appears to be back in place). This forces folks who were using/pinned on 2.4.0 to upgrade to 2.5.1. Is this expected or is there still ongoing work to get multi-arch builds retroactively created for versions < 2.5.1?

Hey @agershman, is it something stopping for the operator upgrade to 2.5.1? After the repo was migrated to the opensearch-project org it was unexpected the old images are removed from ECR, so at this point might need to get approvals for all the backfill versions (for all versions <2.5.0).
Adding @bbarani

agershman · 2024-02-03T18:39:41Z

@prudhvigodithi I wanted to circle back on my earlier comment. I'm seeing that the reestablished helm chart and referenced image at version 2.5.1 does indeed include multi-arch support (e.g. linux/amd64 and linux/arm64). What I am however not seeing is that previous existing versions (e.g. 2.4.0) do not include much-arch support (i.e. only linux/amd64 appears to be back in place). This forces folks who were using/pinned on 2.4.0 to upgrade to 2.5.1. Is this expected or is there still ongoing work to get multi-arch builds retroactively created for versions < 2.5.1?

Hey @agershman, is it something stopping for the operator upgrade to 2.5.1? After the repo was migrated to the opensearch-project org it was unexpected the old images are removed from ECR, so at this point might need to get approvals for all the backfill versions (for all versions <2.5.0). Adding @bbarani

Nothing stopping us given the changes in 2.5.0 and 2.5.1 being non-functional. Just was curious if it was expected that versions prior to 2.5.1 would be back but not include multi-arch support. Our path forward will have to be bump to 2.5.1 which again is fine given the diff.

prudhvigodithi · 2024-02-03T18:44:56Z

Just to add @welkson, the following are steps I have tried and looks green, can you please check ?

Install 2.5.0

helm install opensearch-operator opensearch-operator/opensearch-operator --version 2.5.0 --set manager.image.repository=opensearchproject/opensearch-operator  --set manager.image.tag=2.5.0

Apply the manifest file

apiVersion: opensearch.opster.io/v1
kind: OpenSearchCluster
metadata:
  name: pgcluster
  namespace: default
spec:
  security:
    config: 
    tls:
       http:
         generate: true 
       transport:
         generate: true
         perNode: true
  general:
    httpPort: 9400
    serviceName: my-first-cluster
    version: 2.11.0
    pluginsList: ["https://github.com/aiven/prometheus-exporter-plugin-for-opensearch/releases/download/2.11.0.0/prometheus-exporter-2.11.0.0.zip"]
    drainDataNodes: true
  dashboards:
    version: 2.11.0
    enable: true
    replicas: 1
    resources:
      requests:
         memory: "512Mi"
         cpu: "200m"
      limits:
         memory: "512Mi"
         cpu: "200m"
  nodePools:
    - component: masters
      replicas: 3
      additionalConfig:
        path.repo: '["/tmp/snapshots"]'
      resources:
         requests:
            memory: "1Gi"
            cpu: "550m"
         limits:
            memory: "1Gi"
            cpu: "550m"
      roles:
        - "data"
        - "cluster_manager"
      persistence:
         emptyDir: {}

Upgrade the operator to 2.5.1

helm upgrade opensearch-operator opensearch-operator/opensearch-operator --version 2.5.1 --set manager.image.repository=opensearchproject/opensearch-operator  --set manager.image.tag=2.5.1


helm ls 
NAME               	NAMESPACE	REVISION	UPDATED                           	STATUS  	CHART                    	APP VERSION
opensearch-operator	default  	2       	2024-02-03 10:43:33.3483 -0800 PST	deployed	opensearch-operator-2.5.1	2.5.1

Re-apply the manifest file.

k apply -f cluster.yaml 
opensearchcluster.opensearch.opster.io/pgcluster unchanged

prudhvigodithi · 2024-02-03T18:45:59Z

Nothing stopping us given the changes in 2.5.0 and 2.5.1 being non-functional. Just was curious if it was expected that versions prior to 2.5.1 would be back but not include multi-arch support. Our path forward will have to be bump to 2.5.1 which again is fine given the diff.

Thanks @agershman, I will keep you posted here once I have enough information about the backfill.

welkson · 2024-02-03T22:54:33Z

Just to add @welkson, the following are steps I have tried and looks green, can you please check ?

Install 2.5.0
helm install opensearch-operator opensearch-operator/opensearch-operator --version 2.5.0 --set manager.image.repository=opensearchproject/opensearch-operator  --set manager.image.tag=2.5.0

Hi @prudhvigodithi ! It worked properly. Thank you ;-)

prudhvigodithi · 2024-02-13T22:39:38Z

Closing this issue as the operator images are now published to OpenSearch DockerHub and ECR registries , please feel-free to re-open if required.
Thanks
Adding @bbarani

vkumar85 added bug Something isn't working untriaged Issues that have not yet been triaged labels Jan 25, 2024

prudhvigodithi mentioned this issue Jan 27, 2024

Revert to use the opster API's and onboard to OpenSearch universal release mechanism #710

Merged

teddyphreak added a commit to nephelaiio/ansible-role-k8s that referenced this issue Jan 28, 2024

Remove opensearch scenario from ci workflows

e7e6c4b

Operator is uninstallable See issue opensearch-project/opensearch-k8s-operator#709

prudhvigodithi closed this as completed in 81db8a3 Jan 30, 2024

prudhvigodithi reopened this Jan 30, 2024

prudhvigodithi mentioned this issue Jan 31, 2024

Update references to default admin credentials #692

Closed

prudhvigodithi mentioned this issue Jan 31, 2024

Update developing.md and add THIRD_PARTY_NOTICES #712

Merged

prudhvigodithi mentioned this issue Feb 1, 2024

Update Jenkinsfile to add ECR staging registry #713

Merged

prudhvigodithi mentioned this issue Feb 1, 2024

Jenkinsfile bug and prepare for 2.5.0 release #714

Merged

prudhvigodithi mentioned this issue Feb 2, 2024

Prepare Release 2.5.1 #716

Merged

prudhvigodithi removed the untriaged Issues that have not yet been triaged label Feb 2, 2024

prudhvigodithi added this to OpenSearch Engineering Effectiveness Feb 2, 2024

github-project-automation bot moved this to Backlog in OpenSearch Engineering Effectiveness Feb 2, 2024

prudhvigodithi self-assigned this Feb 2, 2024

prudhvigodithi mentioned this issue Feb 2, 2024

Readme update #720

Merged

prudhvigodithi mentioned this issue Feb 5, 2024

[BUG] Bad release notes for 2.5.0 #721

Closed

bbarani moved this from Backlog to In review in OpenSearch Engineering Effectiveness Feb 12, 2024

prudhvigodithi closed this as completed Feb 13, 2024

github-project-automation bot moved this from In review to Done in OpenSearch Engineering Effectiveness Feb 13, 2024

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Back-off pulling image "public.ecr.aws/opsterio/opensearch-operator:2.3.1"[BUG] #709

Back-off pulling image "public.ecr.aws/opsterio/opensearch-operator:2.3.1"[BUG] #709

vkumar85 commented Jan 25, 2024

pomyslowynick commented Jan 25, 2024 •

edited

Loading

Rockawear commented Jan 25, 2024

evheniyt commented Jan 26, 2024

mustafaonure commented Jan 26, 2024

swoehrl-mw commented Jan 26, 2024

salyh commented Jan 26, 2024

swoehrl-mw commented Jan 26, 2024

rybnico commented Jan 26, 2024 •

edited

Loading

prudhvigodithi commented Jan 26, 2024

jashandeep-sohi commented Jan 26, 2024

roskee commented Jan 29, 2024

BobakMariusz commented Jan 29, 2024

sunsrin commented Jan 29, 2024 •

edited

Loading

prudhvigodithi commented Jan 30, 2024

agershman commented Jan 31, 2024 •

edited

Loading

prudhvigodithi commented Jan 31, 2024

jashandeep-sohi commented Jan 31, 2024

prudhvigodithi commented Jan 31, 2024

mrvdcsg commented Feb 1, 2024

prudhvigodithi commented Feb 2, 2024

prudhvigodithi commented Feb 2, 2024

prudhvigodithi commented Feb 2, 2024

welkson commented Feb 3, 2024 •

edited

Loading

agershman commented Feb 3, 2024

prudhvigodithi commented Feb 3, 2024 •

edited

Loading

prudhvigodithi commented Feb 3, 2024

agershman commented Feb 3, 2024

prudhvigodithi commented Feb 3, 2024

prudhvigodithi commented Feb 3, 2024

welkson commented Feb 3, 2024

prudhvigodithi commented Feb 13, 2024

Back-off pulling image "public.ecr.aws/opsterio/opensearch-operator:2.3.1"[BUG] #709

Back-off pulling image "public.ecr.aws/opsterio/opensearch-operator:2.3.1"[BUG] #709

Comments

vkumar85 commented Jan 25, 2024

What is the bug?

How can one reproduce the bug?

What is the expected behavior?

What is your host/environment?

Do you have any screenshots?

Do you have any additional context?

pomyslowynick commented Jan 25, 2024 • edited Loading

Rockawear commented Jan 25, 2024

evheniyt commented Jan 26, 2024

mustafaonure commented Jan 26, 2024

swoehrl-mw commented Jan 26, 2024

salyh commented Jan 26, 2024

swoehrl-mw commented Jan 26, 2024

rybnico commented Jan 26, 2024 • edited Loading

prudhvigodithi commented Jan 26, 2024

jashandeep-sohi commented Jan 26, 2024

roskee commented Jan 29, 2024

BobakMariusz commented Jan 29, 2024

sunsrin commented Jan 29, 2024 • edited Loading

prudhvigodithi commented Jan 30, 2024

agershman commented Jan 31, 2024 • edited Loading

prudhvigodithi commented Jan 31, 2024

jashandeep-sohi commented Jan 31, 2024

prudhvigodithi commented Jan 31, 2024

mrvdcsg commented Feb 1, 2024

prudhvigodithi commented Feb 2, 2024

prudhvigodithi commented Feb 2, 2024

prudhvigodithi commented Feb 2, 2024

welkson commented Feb 3, 2024 • edited Loading

agershman commented Feb 3, 2024

prudhvigodithi commented Feb 3, 2024 • edited Loading

prudhvigodithi commented Feb 3, 2024

agershman commented Feb 3, 2024

prudhvigodithi commented Feb 3, 2024

prudhvigodithi commented Feb 3, 2024

welkson commented Feb 3, 2024

prudhvigodithi commented Feb 13, 2024

pomyslowynick commented Jan 25, 2024 •

edited

Loading

rybnico commented Jan 26, 2024 •

edited

Loading

sunsrin commented Jan 29, 2024 •

edited

Loading

agershman commented Jan 31, 2024 •

edited

Loading

welkson commented Feb 3, 2024 •

edited

Loading

prudhvigodithi commented Feb 3, 2024 •

edited

Loading