UNCLASSIFIED

Commit 07f95242 authored by gavin.scallon's avatar gavin.scallon
Browse files

Version update to 1.6.1

parent c8d05ac0
Pipeline #21521 passed with stage
......@@ -4,14 +4,14 @@ ARG BASE_REGISTRY=nexus-docker-secure.levelup-dev.io
ARG BASE_IMAGE=redhat/ubi/ubi8
ARG BASE_TAG=8.2
###############################################################
FROM opensource/istio/operator/operator:1.6.0 AS base
FROM opensource/istio/operator/operator:1.6.1 AS base
FROM ${BASE_REGISTRY}/${BASE_IMAGE}:${BASE_TAG}
# Provide label information
LABEL name="istio-operator" \
maintainer="cody.hutchins@darkwolf.co" \
vendor="Open Source" \
version="1.6.0" \
version="1.6.1" \
release="1" \
summary="Operator for Istio" \
description="The istio-operator allows you to package, deploy, and manage Istio in Kubernetes"
......
@Library('DCCSCR@master') _
dccscrPipeline( version: "1.6.0")
\ No newline at end of file
dccscrPipeline( version: "1.6.1")
\ No newline at end of file
......@@ -89,7 +89,7 @@ This ensures that the hub being used as a source for image-pulling is the privat
2. The second workaround requires a deeper dive into the code and requires you to download the Istio from the releases page:
https://github.com/istio/istio/releases/tag/1.6.0
https://github.com/istio/istio/releases/tag/1.6.1
Un-tar the download file and move it to the location on the machine of your choice.
......@@ -99,8 +99,8 @@ Navigate to the `install/kubernetes/operator/charts` directory. You will see var
In order to use these external charts, run the following command (this example is using the default profile):
`istioctl manifest apply --set installPackagePath=< path to istio releases >/istio-1.6.0/install/kubernetes/operator/charts \
--set profile=< path to istio releases >/istio-1.6.0/install/kubernetes/operator/profiles/default.yaml`
`istioctl manifest apply --set installPackagePath=< path to istio releases >/istio-1.6.1/install/kubernetes/operator/charts \
--set profile=< path to istio releases >/istio-1.6.1/install/kubernetes/operator/profiles/default.yaml`
You should then see the Iron Bank container images used in the Istio deployment.
......
---
resources:
- url: "docker://docker.io/istio/operator@sha256:0132f1ec4a7b492424eb32c17ab68cb01ccd169d7b664f460107655e15cb9bba"
tag: "opensource/istio/operator/operator:1.6.0"
- url: "docker://docker.io/istio/operator@sha256:8fba2ac670f38ca768966c6789d044039f30cca4de372d073f7e64e7245e671c"
tag: "opensource/istio/operator/operator:1.6.1"
  • Pipeline Status: SUCCESS
    Branch: 1.6.1-update

    graph LR
      0([setup]):::INTERNAL_SUCCESS --> 1([Import Artifacts]):::SUCCESS --> 2((/)):::INTERNAL_SUCCESS --> 3([Stage Artifacts]):::SUCCESS --> 4((/)):::INTERNAL_SUCCESS --> 5([Build]):::SUCCESS --> 6([Publish, Scan & Report]):::INTERNAL_NOT_BUILT
    
    classDef SUCCESS font-size:10px
    classDef FAILURE fill:#f44, font-size:10px
    classDef SKIPPED font-size:10px
    classDef ABORTED fill:#889, font-size:10px
    classDef INTERNAL_SUCCESS font-size:10px, stroke-dasharray: 2, 1
    classDef INTERNAL_FAILURE fill:#f44, font-size:10px, stroke-dasharray: 2, 1
    classDef INTERNAL_SKIPPED font-size:10px, stroke-dasharray: 2, 1
    classDef INTERNAL_ABORTED fill:#889, font-size:10px, stroke-dasharray: 2, 1
    
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment