delete

[ghost]

I've finally learned what "upward compatible" means.  It means we get to
keep all our old mistakes.
		-- Dennie van Tassel

[othercorey]

I had to revert to 1.16.0 to get my images to push to remote repository at all.

[briandealwis]

Hi @othercorey. Do you have any settings for local-cluster in your ~/.skafold/config file? Could you include the output of running with -v debug?

There were some changes to this with #5012, but when I run with docker-desktop, I see push-images being set to false:

...
INFO[0000] applying profile: docker-desktop             
...
INFO[0000] Using kubectl context: docker-desktop        
DEBU[0000] Using builder: local                         
...
DEBU[0000] push value not present, defaulting to false because cluster.PushImages is false 

[gsquared94]

@braderhart I'm wondering if the profile isn't being applied correctly. Can you try embedding this build stanza directly in the main pipeline instead of using a profile and see if you still encounter this issue?

apiVersion: skaffold/v2beta10
kind: Config

build:
  local:
    useBuildkit: true
  artifacts:
  - context: docker/aria2
    docker:
      buildArgs:
        ARIA2_VERSION: 1.35.0
      noCache: true
    image: equalos/aria2
  tagPolicy:
    envTemplate:
      template: alpine

metadata:
  name: aria2

[briandealwis]

And can you include your ~/.skaffold/config too please?

[briandealwis]

@braderhart do you have any other contexts defined? (specifically non-local clusters)

[tejal29]

hmm looks like when you specify the kube-context, we grab the local-cluster bool and detect its a local cluster.

kubeContexts:
- kube-context: docker-desktop
  local-cluster: true

May be there is a bug on how we apply profiles.

[aaron-prindle]

@tejaldesai were you able to reproduce this issue? I wasn't sure from your above comment, currently this has needs-reproduction

[gsquared94]

seems like a dupe of #5334

[nkubala]

@braderhart can you confirm this is still an issue on the latest version of skaffold (or any version later than v1.27.0)? it seems that this has been fixed in #6024 but I want to be sure before closing this issue.