[elasticsearch-operator] Bump golang builder image to 1.13

[periklis]

Motivation

Reflects the upcoming change for elasticsearch-operator in openshift/elasticsearch-operator#277

[openshift-ci-robot]

@periklis: The following tests failed, say /retest to rerun all failed tests:

Test name	Commit	Details	Rerun command
ci/rehearse/openshift/elasticsearch-operator/master/unit-build01	10f1909	link	/test pj-rehearse
ci/rehearse/openshift/elasticsearch-operator/release-4.5/unit-build01	da0240c6874bd60bc3ef2cedb202e7d8cc312507	link	/test pj-rehearse
ci/rehearse/openshift/elasticsearch-operator/release-4.5/images-build01	da0240c6874bd60bc3ef2cedb202e7d8cc312507	link	/test pj-rehearse

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[vimalk78]

/lgtm

[periklis]

/test pj-rehearse

[periklis]

/test pj-rehearse

[periklis]

/test pj-rehearse

[periklis]

/retest

[droslean]

/test pj-rehearse

[periklis]

/assign @jcantrill

[periklis]

@jcantrill This is the follow-up for openshift/elasticsearch-operartor#277 to bump CI to golang-1.13. We can skip the failing rehearse job ci/rehearse/openshift/elasticsearch-operator/master/unit-build01 according to dptp-helpdesk since the job is not existing anymore.

[jcantrill]

/retest

[jcantrill]

/lgtm

[jcantrill]

/approve

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jcantrill, periklis, vimalk78

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• ci-operator/config/openshift/elasticsearch-operator/OWNERS [jcantrill]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-bot]

/retest

Please review the full test history for this PR and help us cut down flakes.

[openshift-ci-robot]

@periklis: Updated the following 5 configmaps:

• ci-operator-master-configs configmap in namespace ci at cluster default using the following files:
  • key openshift-elasticsearch-operator-master.yaml using file ci-operator/config/openshift/elasticsearch-operator/openshift-elasticsearch-operator-master.yaml
• ci-operator-master-configs configmap in namespace ci-stg at cluster default using the following files:
  • key openshift-elasticsearch-operator-master.yaml using file ci-operator/config/openshift/elasticsearch-operator/openshift-elasticsearch-operator-master.yaml
• ci-operator-master-configs configmap in namespace ci at cluster app.ci using the following files:
  • key openshift-elasticsearch-operator-master.yaml using file ci-operator/config/openshift/elasticsearch-operator/openshift-elasticsearch-operator-master.yaml
• ci-operator-master-configs configmap in namespace ci-stg at cluster app.ci using the following files:
  • key openshift-elasticsearch-operator-master.yaml using file ci-operator/config/openshift/elasticsearch-operator/openshift-elasticsearch-operator-master.yaml
• ci-operator-master-configs configmap in namespace ci at cluster ci/api-build01-ci-devcluster-openshift-com:6443 using the following files:
  • key openshift-elasticsearch-operator-master.yaml using file ci-operator/config/openshift/elasticsearch-operator/openshift-elasticsearch-operator-master.yaml

In response to this:

Motivation

Reflects the upcoming change for elasticsearch-operator in openshift/elasticsearch-operator#277

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.