The output of `oc new-build

Summary

asGitHubCommit uses commit.Author to extract the author of a commit. This is the GitHub user profile of the author, not the information specified in the commit. That's in commit.Commit.Author.

func (p *GitHubProvider) asGitHubCommit(commit *github.RepositoryCommit) GitCommit {
	message := ""
	if commit.Commit != nil {
		message = util.DereferenceString(commit.Com

I have setup an eks registry, but am unsure as to how to push the aquasec image to it. the 'ref'. Do I do a 'docker build -t aquasec:latest' in the source directory, push the container to ecr, and then reference it there? some example cli would be very useful.

General information

• Minishift version:

minishift version
minishift v1.22.0+7163416

• OS: Linux
• Hypervisor: KVM (in nested VM in VMware)

Steps to reproduce

[root@TSKERCBOFRAP01 ~]# printenv |grep NO_PROXY
NO_PROXY=localhost

minishift start
-- Starting profile 'minishift'
-- Using proxy for the setup
-- Check if deprecated options are used ...

Description

I'm trying to set up openshift-3.11 on CentOS-7 on VirtualBox VMs:

cat /etc/redhat-release
CentOS Linux release 7.6.1810 (Core)

# cat /etc/os-release
NAME="CentOS Linux"
VERSION="7 (Core)"
ID="centos"
ID_LIKE="rhel fedora"
VERSION_ID="7"
PRETTY_NAME="CentOS Linux 7 (Core)"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:centos:centos:7"
HOME_URL="https://www.centos.o

See the video attached:

First time: Hitting the search button. Outcome: expected.
Second time: Return keystroke hit. Outcome: unexpected. Reloads the page. It should perform the exact action as the first time.

Exception in thread "main" java.lang.ClassCastException: io.fabric8.kubernetes.api.model.IntOrStringBuilder cannot be cast to io.fabric8.kubernetes.api.model.ObjectMetaBuilder
at io.fabric8.kubernetes.api.builder.BaseFluent.acceptInternal(BaseFluent.java:118)
at io.fabric8.kubernetes.api.builder.BaseFluent.accept(BaseFluent.java:109)
at io.fabric8.kubernetes.api.builder.BaseFluent.accept(Bas

Suggestion / Problem
As I was trying Strimzi for the first time, I was following the Quickstarts doc to run a single-node Kafka cluster but the Docker container for the Kafka node was failing with the following error:

Liveness probe failed: OCI runtime exec failed: exec failed: container_linux.go:345: starting container process caused "process_linux.go:91: executing setns process caused

Kind of issue

Bug

Observed behavior

Via code inspection it was noted that any operations on the heketi db done outside the lock may change the content of heketi.db while another heketi instance has the file locked.

Expected/desired behavior

DB changes should be done under a lock

Other useful information

Thanks to @ShyamsundarR for noticing this.

Hi, can you write small example, how to use this image in docker-compose.yml?

环境信息：

KubeOperator版本：2.1.0

浏览器版本：Chorme 77.0.3865.90

云提供商：vsphere

One needs to click on this before entering login/password, which can be confusing.

Problem:

Kedge fails on creating OpenShift artifacts with error: error: unable to recognize "STDIN": no matches for apps.openshift.io/, Kind=DeploymentConfig

Steps to reproduce:

Using this kedge file:

$ cat kedge.yml 
controller: deploymentconfig
containers:
- image: centos/httpd
name: web
services:
- portMappings:
  - 8080:80

Now feeding it to opens