#codefresh - September 2019

Anybody have any hints for deploying an EKS cluster via Codefesh, the example in their repo fails as described in the CF repo issue https://github.com/codefresh-io/eks-installer/issues/5

Let me escalate this to engineering.

I do not have another example of automated creation and addition in a pipeline looks like this needs a fix to the API call responsible for adding the EKS cluster to our Kubernetes cluster integration.

Awesome, 10pm here - that sounds like my home/bed time as im a total newbie and could not help other that test works after a change

thanks @dustinvb

Hey, general question - say I've built a docker image in a codefresh pipeline (tagged in the CF registry and also pushed out to ECR) and want to use that as the image in a different pipelines freestyle step - how do I auth to the private registry to pull the image?
Dont mind if CF is the easiest, but can't seem to find a way to use my ECR credentials which let me push images to also pull images?

#office-hours starting now! ask questions, get answers. free for everyone. https://zoom.us/j/508587304

So - I've got a new pipeline stuck in "pending" state - is there any way to get info on what that means / why that is? zero other builds are running

anyone running codefresh pipeline invoked by another pipeline successfully with variables being passed in? (the official step is called codefresh-run) the pipeline being invoked doesn’t seem to be getting the variables for me 😕

i think the cloudposse example app might have that... i have a "release" pipeline that triggers off a github release, and it calls deploy pipelines conditionally based on the release tag format

We have a disabled trigger on the target pipeline, but I can't quite remember what that solved at the moment

yeah im using their official codefresh-run step instead of invoking the cli, i might just end up going back to the cli command

Spinnaker vs Codefresh? Thoughts 👋

Sorry, I haven't been that active in this channel. Been a busy summer. If anyone ever has a question relating to Codefresh just ping me on here using @dustinvb and I'll get back to you ASAP

You can also ping me, @Kristofer Svardstal, and I will try to assist! 😄

Morning guys

Struggling here, a pipe was working now failing -- big change could be is my EKS was bumped from 1.13 to 1.14

Executing command: /cf-deploy-kubernetes /codefresh/volume/cf-generated/deployment.yml
Server minor version: 14
Warning: No variable was found in /codefresh/volume/cf-generated/deployment.yml, syntax is {{VAR}}
---> Kubernetes objects to deploy in /codefresh/volume/cf-generated/deployment.yml :

Nothing obvious to me - I've put YAML in the pipe from prior working runs

Can you share the pipeline yaml?

So, I'm having an issue. I'm trying to conditionally do a pipeline step based off both a condition and an approval step match, but I can't find the right YAML voodoo to make it work, and there are ZERO examples that I can find in the docs as well.

example yaml step:

  deploy_helmfile_sqitch:
    title: Deploy with helmfile
    stage: Deploy
    image: "${{TOOL_DOCKER_REPO_PREFIX}}/${{AWS_ENV_NAME}}:latest"
    working_directory: /conf/
    environment:
      - 'KUBECONFIG=${{CF_KUBECONFIG_PATH}}'
      - 'REPO_ROOT=${{CF_VOLUME_PATH}}/${{CF_REPO_NAME}}'
    shell: bash
    commands:
      # Announce the release version
      - echo "* Preparing to deploy ${RELEASE_NAME} with image ${IMAGE_NAME}:${IMAGE_TAG}"
      - echo "*     with flavor \"$FLAVOR\" into namespace ${RELEASE_NAMESPACE}"
      - kubectl config use-context "${KUBE_CONTEXT}"
      - cd $(conf-directory helmfiles) && echo Working directory is now $PWD
      - helmfile --namespace="${RELEASE_NAMESPACE}" --environment="${FLAVOR}"
        -f "${REPO_ROOT}/deploy/releases/sqitch.yaml" sync
    when:
      steps:
      - name: ask_for_permission
        on:
        - approved
      conditions:
        any:
          comment_is_not_airflow: '"${{COMMENT}}" != "airflow"'

@Igor Rodionov ☝️

Any tips

Afternoon. Im rebuilding my k8s and codefresh - my first, built two weeks back, got tangled.
When i try to delete or edit a service in kube-system i hit replicasets.extensions is forbidden: User "system:serviceaccount:kube-system:codefresh-user" cannot list resource "replicasets" in API group "extensions" in the namespace "kube-system".

This has been applied without error - which i thought would give control to the SA codefresh user over kube-system

Ignore above - the problem here was the nodes did not fully come up on the az, fixed my terraform and now working

Im hitting an RBAC problem,

Message             services "dev-mm-user-fe-default-srv" is forbidden: User                                                                                
                     "system:serviceaccount:kube-system:codefresh-user" cannot get resource "services" in API group ""                                       
                     in the namespace "eu-dev-public-ns"     

Ive applying the following, that i hoped would allow DF to deploy to this ns/svc - but didnt

apiVersion: <http://rbac.authorization.k8s.io/v1|rbac.authorization.k8s.io/v1>
kind: ClusterRoleBinding
metadata:
  name: codefresh-user
roleRef:
  apiGroup: <http://rbac.authorization.k8s.io|rbac.authorization.k8s.io>
  kind: ClusterRole
  name: codefresh-role
subjects:
- kind: ServiceAccount
  name: codefresh-user
  namespace: eu-dev-public-ns

any hints would be greatly received

We use Helmfile and deploy the Codefresh account like this

Not sure if it is helpful...

Hi @Erik Osterman (Cloud Posse) thanks for the link - it might be useful.
I'm very much learning as i go, do i need to add this as a helm repo ?

will read on helmfile.d

Actually Helmfile is a way to manage helm releases

Helmfile will add the repos for you

We also have a #helmfile channel

Read more about it here

same troubles

services "dev-mm-user-fe-default-srv" is forbidden: User "system:serviceaccount:kube-system:codefresh-service-account" cannot update resource "services" in API group "" in the namespace "eu-dev-public-ns"

public #office-hours starting now! join us to talk shop https://zoom.us/j/508587304

Codefresh Incident - Builds are stuck in pending
Sep 20, 17:16 UTC
Update - We are continuing to investigate this issue.Sep 20, 17:15 UTC
Investigating - Currently we're investigating an issue that's affecting the execution of builds in the system.

Codefresh Incident - Builds are stuck in pending
Sep 20, 18:21 UTC
Identified - Issue identified:
We are experiencing a connectivity issue with a third-party vendor, which affects the scheduling flow for our builds.
The ETA to resolve this issue is ~1 hour.Sep 20, 17:16 UTC
Update - We are continuing to investigate this issue.Sep 20, 17:15 UTC
Investigating - Currently we're investigating an issue that's affecting the execution of builds in the system.

whats up with codefresh today?

down

Codefresh Incident - Builds are stuck in pending
Sep 20, 18:21 UTC
Identified - Issue identified:
We are experiencing a connectivity issue with GCP Cloud SQL (PostgreSQL) which affects the scheduling flow for our builds.
The ETA to resolve this issue is ~1 hour.Sep 20, 17:16 UTC
Update - We are continuing to investigate this issue.Sep 20, 17:15 UTC
Investigating - Currently we're investigating an issue that's affecting the execution of builds in the system.

Yeah, UI is broken too - teammate is getting the new user experience~

We are on it, will update once we back

my coworkers first day using the app as well 😕

Codefresh Incident - Builds are stuck in pending
Sep 20, 20:45 UTC
Update - We are continuing to monitor for any further issues.Sep 20, 20:34 UTC
Monitoring - Builds are currently able to be executed.
We're still monitoring the system.Sep 20, 18:21 UTC
Identified - Issue identified:
We are experiencing a connectivity issue with GCP Cloud SQL (PostgreSQL) which affects the scheduling flow for our builds.
The ETA to resolve this issue is ~1 hour.Sep 20, 17:16 UTC
Update - We are continuing to investigate this issue.Sep 20, 17:15 UTC...

We are back

the status page will be updated now as well

Codefresh Incident - Builds are stuck in pending
Sep 20, 21:04 UTC
Update - Builds are able to progress now.
We're still investigating an issue with our Helm-repository integration and audit-log data availability.Sep 20, 20:45 UTC
Update - We are continuing to monitor for any further issues.Sep 20, 20:34 UTC
Monitoring - Builds are currently able to be executed.
We're still monitoring the system.Sep 20, 18:21 UTC
Identified - Issue identified:
We are experiencing a connectivity issue with GCP Cloud SQL (PostgreSQL) which affects the...

Codefresh Incident - Builds are stuck in pending
Sep 20, 21:36 UTC
Update - We are continuing to monitor for any further issues.Sep 20, 21:36 UTC
Update - Helm-repository integration is working now.
Old audit-log data will be available soon.Sep 20, 21:04 UTC
Update - Builds are able to progress now.
We're still investigating an issue with our Helm-repository integration and audit-log data availability.Sep 20, 20:45 UTC
Update - We are continuing to monitor for any further issues.Sep 20, 20:34 UTC
Monitoring - Builds are currently able to be...

Codefresh Incident - Builds are stuck in pending
Sep 20, 22:23 UTC
Resolved - Issue related to stuck builds is completely resolvedSep 20, 21:36 UTC
Update - We are continuing to monitor for any further issues.Sep 20, 21:36 UTC
Update - Helm-repository integration is working now.
Old audit-log data will be available soon.Sep 20, 21:04 UTC
Update - Builds are able to progress now.
We're still investigating an issue with our Helm-repository integration and audit-log data availability.Sep 20, 20:45 UTC
Update - We are continuing to monitor for...

Old Audit-log data is not available
Sep 20, 22:29 UTC
Identified - We're currently working on restoring the old audit log data. It wil be available soon

GitHub has reported an incident
Sep 24, 12:44 UTC
Investigating - GitHub has reported an incident
This might impact your builds.

More information here: https://www.githubstatus.com/incidents/b54zv9nz8m01

GitHub has reported an incident
Sep 24, 14:28 UTC
Resolved - This incident has been resolved.Sep 24, 12:44 UTC
Investigating - GitHub has reported an incident
This might impact your builds.

More information here: https://www.githubstatus.com/incidents/b54zv9nz8m01