APT Package Installation Improvements

[jasdeep-hundal]

Is this a BUG REPORT or FEATURE REQUEST? (choose one): FEATURE REQUEST

Proposing two improvements around APT package installation:

1. Removing the explicit install of the python-apt package during preinstall:

   • The Ansible 'apt' module actually lists 'python-apt' as a dependency, so we wouldn't expect this to work anyways.
   • The reason it does is that Ansible automatically installs python-apt upon the first usage of the "apt" module.
   • Will have patch up for this shortly.

2. Adding the ability to skip APT package management cache updates:

   • Two use cases on my end:
     • Being able to test deployment offline.
     • Increasing idempotence when debugging deployment issues. Even though the risk of package updates breaking something is small, would rather totally rule that out when investigating.
   • I can add a two line hack to get around this, would be nice if there was a clean option though.
   • Happy to work on a patch for this as well, but that might be delayed for a bit. Also, I'm guessing we don't want divergence between APT and YUM behavior, so:
     • Slightly worried about testing against Yum because I haven't run Kubespray against a system using it yet.
     • Will probably need a bit more back and forth with Kubespray devs before settling on the right way to do this.

[jasdeep-hundal]

Patch for the first request is here: #2285

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.