Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Switch to new machine type in semaphore CI #3462

Merged
merged 1 commit into from
Aug 15, 2024

Conversation

tmjd
Copy link
Member

@tmjd tmjd commented Aug 15, 2024

Description

For PR author

  • Tests for change.
  • If changing pkg/apis/, run make gen-files
  • If changing versions, run make gen-versions

For PR reviewers

A note for code reviewers - all pull requests must have the following:

  • Milestone set according to targeted release.
  • Appropriate labels:
    • kind/bug if this is a bugfix.
    • kind/enhancement if this is a a new feature.
    • enterprise if this PR applies to Calico Enterprise only.

@@ -2,7 +2,7 @@ version: v1.0
name: Operator CD
agent:
machine:
type: e1-standard-4
type: f1-standard-4
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this can actually be f1-standard-2, I think these machines are bigger. The 4 is apparently much larger, might want to check with @sujeet-kr though.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes e1-standard-4's can be replaced with f1-standard-2s, if the reason for using e1-standard-4 was memory and storage.

Suggested change
type: f1-standard-4
type: f1-standard-2

@@ -137,7 +137,7 @@ blocks:
task:
agent:
machine:
type: e1-standard-4
type: f1-standard-4

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
type: f1-standard-4
type: f1-standard-2

Copy link

@sujeet-kr sujeet-kr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants