Skip to content

Instantly share code, notes, and snippets.

View dgozalo's full-sized avatar

Daniel Gozalo dgozalo

View GitHub Profile
@dgozalo
dgozalo / Cipher.java
Last active May 5, 2019 00:14
Cipher / Decipher
import java.io.IOException;
import java.nio.file.Files;
import java.nio.file.Paths;
import java.util.*;
import java.util.stream.Collectors;
import java.util.stream.Stream;
public class Cipher {
getting the log for build dg-bee/environment-marescratch-dev/master #5 promotion stage from build pack and container build-step-build-helm-apply
Modified file /workspace/source/env/Chart.yaml to set the chart to version 5
WARNING: No $CHART_REPOSITORY defined so using the default value of: http://jenkins-x-chartmuseum:8080
Adding missing Helm repo: chartmuseum.jenkins-x.io http://chartmuseum.jenkins-x.io
Read credentials for http://chartmuseum.jenkins-x.io from vault helm/repos
Successfully added Helm repository chartmuseum.jenkins-x.io.
Adding missing Helm repo: jenkins-x-chartmuseum http://jenkins-x-chartmuseum:8080
Read credentials for http://jenkins-x-chartmuseum:8080 from vault helm/repos
Successfully added Helm repository jenkins-x-chartmuseum.
WARNING: No $CHART_REPOSITORY defined so using the default value of: http://jenkins-x-chartmuseum:8080
Saving the Git authentication configuration
ERROR: error creating cluster configuring the git auth: saving the Git authentication configuration: saving auth config "gitAuth.yaml" in vault: Error making API request.
URL: PUT http://jx-vault-samuraigravel.jx.35.205.217.159.nip.io/v1/secret/data/auth/gitAuth.yaml
Code: 404. Errors:
* no handler for route 'secret/data/auth/gitAuth.yaml'
error: configuring the git auth: saving the Git authentication configuration: saving auth config "gitAuth.yaml" in vault: Error making API request.
URL: PUT http://jx-vault-samuraigravel.jx.35.205.217.159.nip.io/v1/secret/data/auth/gitAuth.yaml
• Failure [885.385 seconds]
Creating application spring-boot-http-gradle
/tmp/jenkins-x/bdd-jx/test/_import/jx_import.go:38
by running jx import
/tmp/jenkins-x/bdd-jx/test/_import/jx_import.go:56
creates an application from the specified folder and promotes it to staging [It]
/tmp/jenkins-x/bdd-jx/test/_import/jx_import.go:57
get applications with a URL
Unexpected error:
Error from server (Invalid): error when applying patch:
{"metadata":{"annotations":{"kubectl.kubernetes.io/last-applied-configuration":"{\"apiVersion\":\"apps/v1\",\"kind\":\"Deployment\",\"metadata\":{\"annotations\":{\"jenkins.io/chart\":\"cm\"},\"labels\":{\"app\":\"cainjector\",\"app.kubernetes.io/instance\":\"jx\",\"app.kubernetes.io/managed-by\":\"Tiller\",\"app.kubernetes.io/name\":\"cainjector\",\"helm.sh/chart\":\"cainjector-v0.9.1\",\"jenkins.io/chart-release\":\"jx\",\"jenkins.io/namespace\":\"cert-manager\",\"jenkins.io/version\":\"1\"},\"name\":\"jx-cainjector\",\"namespace\":\"cert-manager\"},\"spec\":{\"replicas\":1,\"selector\":{\"matchLabels\":{\"app\":\"cainjector\",\"app.kubernetes.io/instance\":\"jx\",\"app.kubernetes.io/managed-by\":\"Tiller\",\"app.kubernetes.io/name\":\"cainjector\"}},\"template\":{\"metadata\":{\"annotations\":null,\"labels\":{\"app\":\"cainjector\",\"app.kubernetes.io/instance\":\"jx\",\"app.kubernetes.io/managed-by\":\"Tiller\",\"app.kubernetes.io/name\":\"cainjector
On AWS we recommend using a custom DNS name to access services in your Kubernetes cluster to ensure you can use all of your Availability Zones
If you do not have a custom DNS name you can use yet, then you can register a new one here: https://console.aws.amazon.com/route53/home?#DomainRegistration:
? Would you like to register a wildcard DNS ALIAS to point at this ELB address? No
The Ingress address <snip>-dd0217b352d06378.elb.us-east-1.amazonaws.com is not an IP address. We recommend we try resolve it to a public IP address and use that for the domain to access services externally.
? Would you like wait and resolve this address to an IP address and use it for the domain? Yes
Waiting for <snip>-dd0217b352d06378.elb.us-east-1.amazonaws.com to be resolvable to an IP address...
WARNING: retrying after error: Address cannot be resolved yet <snip>-dd0217b352d06378.elb.us-east-1.amazonaws.com
.
@dgozalo
dgozalo / pa
Created November 13, 2019 15:44
apiVersion: jenkins.io/v1
kind: PipelineActivity
metadata:
creationTimestamp: "2019-11-12T18:47:22Z"
generation: 1
labels:
branch: master
build: "1"
owner: dgozalo
provider: github
@dgozalo
dgozalo / jxboot-policies.json
Created January 22, 2020 11:05
This is an AWS IAM Policy with all the minimum permissions to let Jenkins X Boot work on EKS
{
"Version": "2012-10-17",
"Statement": [
{
"Sid": "VisualEditor0",
"Effect": "Allow",
"Action": [
"dynamodb:CreateTable",
"s3:GetObject",
@dgozalo
dgozalo / eksctl-policy.json
Created January 22, 2020 11:07
This is an AWS IAM Policy needed by eksctl to create and operate an EKS cluster.
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": [
"iam:CreateInstanceProfile",
"iam:DeleteInstanceProfile",
"iam:GetRole",
"iam:GetInstanceProfile",
panic: runtime error: invalid memory address or nil pointer dereference │
│ [signal SIGSEGV: segmentation violation code=0x1 addr=0x18 pc=0x576112] │
│ │
│ goroutine 814 [running]: