[installer] use image digest for redis image

[iQQBot]

Description

[installer] use image digest for redis image

Related Issue(s)

Fixes ENG-1717

How to test

Documentation

Preview status

Gitpod was successfully deployed to your preview environment.

• 🏷️ Name - pd-image-dbfcbfa4290
• 🔗 URL - pd-image-dbfcbfa4290.preview.gitpod-dev.com/workspaces.
• 📚 Documentation - See our internal documentation for information on how to interact with your preview environment.
• 📦 Version - pd-image-digest-redis-gha.23350
• 🗒️ Logs - GCP Logs Explorer

Build Options

Build

• /werft with-werft
  Run the build with werft instead of GHA
• leeway-no-cache
• /werft no-test
  Run Leeway with --dont-test

Publish

• /werft publish-to-npm
• /werft publish-to-jb-marketplace

Installer

• analytics=segment
• with-dedicated-emulation
• workspace-feature-flags
  Add desired feature flags to the end of the line above, space separated

Preview Environment / Integration Tests

• /werft with-local-preview
  If enabled this will build install/preview
• /werft with-preview
• /werft with-large-vm
• /werft with-gce-vm
  If enabled this will create the environment on GCE infra
• /werft preemptible
  Saves cost. Untick this only if you're really sure you need a non-preemtible machine.
• with-integration-tests=all
  Valid options are all, workspace, webapp, ide, jetbrains, vscode, ssh. If enabled, with-preview and with-large-vm will be enabled.
• with-monitoring

/hold

[mustard-mh]

LGTM

[iQQBot]

/hold

wait for https://github.com/gitpod-io/gitpod-dedicated/blob/af8aa69fa964a201c44fa518a55a07c1b00178ed/ops/images/push-images.sh#L21C1-L26C7

[iQQBot]

verify image is correct and we can start workspace

[kylos101]

/hold

wait for https://github.com/gitpod-io/gitpod-dedicated/blob/af8aa69fa964a201c44fa518a55a07c1b00178ed/ops/images/push-images.sh#L21C1-L26C7

Hi @iQQBot , what is left/preventing removal of the hold for this PR? I ask because #19402 landed on Feb 7. I assume there is some other PR or Linear issue or Slack thread remaining. Can you share?

[iQQBot]

@kylos101 not all cell upgrade to this version

[kylos101]

@kylos101 not all cell upgrade to this version

Gotcha, thank you, @iQQBot !

[stale]

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[socket-security]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert	Package	Note
Install scripts	npm/core-js@3.32.0	Install script: postinstall Source: node -e "try{require('./postinstall')}catch(e){}"

View full report↗︎

Next steps

What is an install script?

Install scripts are run when the package is installed. The majority of malware in npm is hidden in install scripts.

Packages should not be running non-essential scripts during install and there are often solutions to problems people solve with install scripts that can be run at publish time instead.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/core-js@3.32.0

[iQQBot]

Tested again, it can start a workspace, and redis pod is healthy

[iQQBot]

/unhold