Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: GoogleCloudPlatform/cloud-sql-proxy-operator
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v0.0.3
Choose a base ref
...
head repository: GoogleCloudPlatform/cloud-sql-proxy-operator
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v0.1.0
Choose a head ref
  • 10 commits
  • 21 files changed
  • 5 contributors

Commits on Dec 8, 2022

  1. Configuration menu
    Copy the full SHA
    a5e7262 View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    2944831 View commit details
    Browse the repository at this point in the history
  3. chore: only run Code Generation on the release-please PRs (#137)

    This change simplifies the github workflow that runs on release PRs. This workflow
    ensures that the generated code in the tagged release is consistent with version.txt.
    hessjcg authored Dec 8, 2022
    Configuration menu
    Copy the full SHA
    2c26d50 View commit details
    Browse the repository at this point in the history
  4. fix: change memory resource to match recommendations Cloud SQL Proxy (#…

    …139)
    
    The Cloud SQL Proxy project recommends 2Gi for ram. This changes the default resource requirements to match.
    hessjcg authored Dec 8, 2022
    Configuration menu
    Copy the full SHA
    a475dd9 View commit details
    Browse the repository at this point in the history

Commits on Dec 12, 2022

  1. chore: remove '-dev' from installer and operator image url (#136)

    The URL for the released image version 0.0.5 now will be:
    cloud-sql-connectors/cloud-sql-operator/cloud-sql-proxy-operator:0.0.5
    
    And the installer URL will now be:
    https://storage.googleapis.com/cloud-sql-connectors/cloud-sql-proxy-operator/v0.0.5/install.sh
    hessjcg authored Dec 12, 2022
    Configuration menu
    Copy the full SHA
    154ba08 View commit details
    Browse the repository at this point in the history
  2. doc: Add quickstart guide to README (#126)

    Adds quickstart instructions to the README. This tells the user how to follow the existing
    Cloud SQL Quickstart on GKE guide, adding a few extra steps in the middle, to try out
    the operator.
    hessjcg authored Dec 12, 2022
    Configuration menu
    Copy the full SHA
    891d6d8 View commit details
    Browse the repository at this point in the history
  3. feat: add user agent to proxy invocation (#122)

    Add the operator version to the proxy's user agent, so that we can track how many people
    are using the operator.
    
    Fixes #67.
    Co-authored-by: Jonathan Hess <hessjc@google.com>
    enocom and hessjcg authored Dec 12, 2022
    Configuration menu
    Copy the full SHA
    803446d View commit details
    Browse the repository at this point in the history
  4. fix: remove unsupported CRD fields and associated code from the proje…

    …ct. (#141)
    
    Removes fields from the CRD and associated code that converts those fields into
    configuration on the proxy container. I removed fields that were unused in existing code
    (like FUSE), fields that were unnecessary for minimum viable use of the proxy (like
    telemetry args), and fields related to unix sockets, since that connection method
    does not yet have an automated e2e test, and proxy V2 preview 4 does not use the
    ?unix-socket=/path exactly as expected.
    hessjcg authored Dec 12, 2022
    Configuration menu
    Copy the full SHA
    3867621 View commit details
    Browse the repository at this point in the history

Commits on Dec 13, 2022

  1. test: add a test to cover resource requirements from spec. (#140)

    While pruning fields from the CRD, I found some uncovered code that needed a test.
    This adds a test case to make sure that when a customer sets the proxy container resource
    requirements in the CRD, the values are actually set on the container.
    hessjcg authored Dec 13, 2022
    Configuration menu
    Copy the full SHA
    977266d View commit details
    Browse the repository at this point in the history
  2. chore(main): release 0.1.0 (#142)

    Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>
    Co-authored-by: Release PR Generate Bot action release-please[bot] <release-please[bot]@users.noreply.github.com>
    release-please[bot] and release-please[bot] authored Dec 13, 2022
    Configuration menu
    Copy the full SHA
    4a88d0d View commit details
    Browse the repository at this point in the history
Loading