Codefresh

Codefresh
GitOps CI/CD platform
Container Orchestration
Continuous Integration
Cloud Infrastructure
DevOps Automation
GitOps
Open roles at Codefresh
0 open roles
No open positions at this time
Closed positions
12 positions
Enterprise Growth Account Executive- Sydney, AU
Remote
Senior
Closed 1 month ago
Business Development Representative
Remote
Entry
Closed 1 month ago
Lead Product Designer
Remote
Lead
Closed 1 month ago
Strategic Account Executive
Remote
Senior
Closed 1 month ago
Senior Accounts Officer
Remote
Senior
Closed 1 month ago
Products and services

Codefresh CI/CD Platform
CI/CD
GI
GitOps Runtime
GitOps
AR
Argo Workflows
Workflow Orchestration

GitOps
DevOps
PR
Progressive Delivery
Deployment

Kubernetes Dashboard
Monitoring

Docker Registry
Container Management

Codefresh Runner
Infrastructure

Pipeline Templates
Templates
TE
Test Management
Testing
HE
Helm Chart Management
Package Management

Application Insights
Analytics
SE
Security Scanning
Security
HE
Helm Charts Management
Package Management
Similar companies

Dagster
Data orchestration platform
San Francisco, CA
51-200 employees
Private

Culture Amp
Australian employee experience platform
Melbourne, Australia
501-1,000 employees
Private
Valuation $2B
53 open jobs

ADTRAN
American telecommunications equipment company
Huntsville, Alabama, United States
1,001-5,000 employees
Public
Valuation $1.2B
117 open jobs

Ceva
Semiconductor IP company for wireless connectivity
Rockville, Maryland, United States
201-500 employees
Public

Appsmith
Open-source platform for building internal tools
Bengaluru, India
51-200 employees
Private
Latest updates
All
X
News
HN
YouTube
How are you structuring ArgoCD at scale?
Lately Iβve been thinking a lot about how folks structure their GitOps repositories and workflows with Argo CD once things start growing. In the beginning everything feels simple: a couple services, maybe one cluster, a staging and a prod environment. Almost any structure works. But after some time the platform grows. More services appear, more clusters, more environments, sometimes more teams. At that point the repository structure and the ApplicationSet strategy suddenly become very important
Β·
4 months ago
Β·
16
Β·
18
Argocd from scratch, in tree structure etc...
Hello Team, I will start work on a new project, I had experience with argocd for 3,4 years already. In past I used similar setup, but services like nginx-ingress, traefik, csi driver installed with HELM and Terraform in separate infrastructure repo, now I want to utilized ArgoCD for that also. I used ArgoCD, but I feel in past I didn't setup in proper way, some thing we did manually, not via code, (as we used management cluster for Argo, we added managed clusters manually,created argo project
Β·
5 months ago
Β·
14
Β·
6
How do you guys run database migrations?
Β·
6 months ago
Β·
6
Β·
4
How to implement environments
I am a PA in CS intern, who is tasked with finding the best practices for trying to build a pipeline, that is going to deploy our IaC in the cloud. I have made a basic pipeline which in the CI stage: \- Selects the deployment environment from the branch name (Main = prod, feature/\* hotfix/\* and bugfix/\* = dev, PR = test) \- Validates the IaC and the deployment stage runs the IaC with the various input variables, to the selected Deployment Environment. But my senior engineer has asked m
Β·
6 months ago
Β·
2
Β·
8
Dynamic AppSet based on cluster labels
I need a sanity check on what I am trying to accomplish because at this point I am not sure it's doable. I currently have a more complex situation than I have had in past experiences using Argo. I have two on prem clusters and a cloud cluster, with a long list of related services I want to deploy with a single appset. Some services only deploy to one on prem cluster, some to both on prem and some to both on prem and the cloud cluster. I have been trying to deploy to the correct clusters using
Β·
7 months ago
Β·
7
Β·
5
Show 15 more
Total Views
2
Total Apply Clicks
0
Total Mock Apply
0
Total Bookmarks
0
Reviews
3.8
46 reviews
Work-life balance
3.4
Compensation
3.9
Culture
4.1
Career
3.6
Management
3.8
76%
Recommend to a friend
Pros
Supportive team and management
Opportunity for career growth
Interesting projects and challenges
Cons
Career progression could be clearer
Room for improvement in processes
Some organizational bureaucracy
Interview experience
50 interviews
Difficulty
3.0
/ 5
Duration
2-5w
Offer rate
34%
Experience
Positive 64%
Neutral 19%
Negative 17%
Interview process
1
Phone Screen
2
Technical Interview
3
Hiring Manager
4
Team Fit
Contact and location